List my articles

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable context beyond annotations: requires an API key, returns a specific shape with fields, notably excludes the article body, and clarifies that 'total' counts all matches, not just the returned page. This goes beyond the structured hints.

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?

Four sentences, each earning its place: purpose+scope, when to use, read-only reassurance/auth, and return shape with a key exclusion. Information-dense without redundancy or fluff.

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?

Though no output schema exists, the description fully covers the return structure, field list, the notable absence of body content, and pagination/authentication details. For a list tool with two optional parameters and strong annotations, this is complete enough for an agent to select and invoke correctly.

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 covers both parameters fully with descriptions, giving a baseline of 3. The description adds meaning by clarifying default status behavior ('including drafts and scheduled posts' when status omitted) and pagination semantics ('total counts all matches, not just the page returned'). This compensates beyond the schema.

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 uses specific verb 'List' with a clear resource: 'articles owned by the authenticated account'. It immediately distinguishes from siblings by noting it is 'the only listing that sees unpublished content' and explicitly contrasts with search_articles, 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?

Provides explicit when-to-use guidance: 'Use this to find your own work' and names the alternative: 'To search across the whole site, including other creators, use search_articles instead.' Also directs users to get_article for body content, covering exclusions and alternatives clearly.

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