Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the burden of disclosing behavior, but it only mentions billing per call and group. It does not state whether it is read-only, pagination behavior, rate limits, or what data is returned (post metadata? content?).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences are concise and front-loaded with the core purpose. However, the second sentence ('Group: Posts. Billing per call: 1 Credits') is low-value metadata that could be omitted or placed in annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is relatively simple with 3 params and no output schema, but the description fails to state expected return format or pagination details. Since annotations are absent, more context is needed to fully guide usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it only mentions 'urn' implicitly ('using its URN') without explaining 'start' and 'cursor' as pagination controls. The parameter examples are in the schema, but the description adds no extra meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool fetches all posts for a given profile URN, which is clear, but it lacks specificity about filtering or pagination and does not differentiate among sibling tools like get_api_v1_posts_info or get_api_v1_posts_featured beyond the 'all' keyword.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool over alternatives, such as when retrieving all posts versus specific post details or featured posts. The description mentions 'For a given profile' but does not explain prerequisites or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.