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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It mentions billing (1 Credit) but lacks details on pagination, error handling, or the nature of 'featured' posts. The read-only nature is implied by 'Get,' but not explicitly stated, and there is no discussion of potential side effects or limits.

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?

The description is a single, focused sentence immediately followed by relevant metadata (Group and Billing). It is front-loaded, contains no fluff, and every part serves a purpose.

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 simple with one parameter, and the description covers the core purpose. However, there is no output schema or mention of response format, pagination, or what 'featured' means in this context. For a minimal GET endpoint, it is adequate but leaves some ambiguity for the agent.

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?

The schema has 0% description coverage for the 'urn' parameter, but the tool description clarifies that the URN belongs to a profile. This adds some meaning beyond the plain schema, though it does not elaborate on format, constraints, or how to obtain the URN. Given the low coverage, this slight compensation earns a middle score.

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 clearly states 'Get all featured posts for a given profile using its URN,' specifying the verb, resource (featured posts), and scope (profile URN). It distinguishes from siblings like get_api_v1_posts_all by explicitly mentioning 'featured,' making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives like get_api_v1_posts_all or get_api_v1_posts_info. It merely states the function without mentioning exclusions, prerequisites, or context for selection among the many post-related tools.

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