list_content

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

No annotations provided; description only mentions listing without disclosing side effects or behavior like sorting. Output schema exists but doesn't mitigate lack of behavioral details.

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?

Very concise and to the point. However, it could be more structured (e.g., bullet points) but no wasted words.

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?

Given 3 parameters, no annotations, and a broad set of siblings, the description is insufficient. It omits what type of content is returned, ordering, and scope of listing.

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?

Description adds value over input schema by specifying content_type options ('static', 'video', 'html5') and clarifying limit/offset for pagination. Schema coverage was 0%, so this is crucial.

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?

Description clearly states 'List uploaded content' with a specific verb and resource. It distinguishes from siblings by being generic, though incomplete.

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 on when to use this tool vs alternatives like list_banners or list_feeds. Context signals show many sibling list tools but description offers no differentiation.

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