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

Annotations already declare readOnlyHint and idempotentHint, covering safety. The description adds meaningful behavioral context: only published case studies are included, category filtering is supported, and cursor-based pagination is used. This goes beyond the annotations without contradicting them.

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 front-loaded sentence that conveys the primary action and resource first, then appends optional modifiers. There is no filler or redundancy, and every phrase adds relevant information.

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?

For a read-only list operation with no required parameters and no output schema, the description conveys the essential behavior: list published case studies, optionally filtered and paginated. It is slightly incomplete in that it does not address how search_portfolio_work relates or describe what fields appear in the returned list, but these are minor gaps given the simple scope.

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 only 33%, so the description must compensate. It explains that category is an optional filter and that cursor enables pagination, but it does not clarify the limit parameter beyond what the schema's min/max constraints imply. Partial compensation for low schema coverage.

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 names a specific action ('List'), a concrete resource ('published kwnva.design case studies'), and scope modifiers ('optional category filter', 'cursor pagination'). It also distinguishes itself from sibling tools: it enumerates case studies rather than fetching a single one, fetching the studio profile, or searching portfolio work.

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 implies when to use the tool: to list published case studies, optionally filtered by category or paginated. However, it does not explicitly explain when to choose this over the sibling search_portfolio_work or fetch_project_case_study, leaving the comparison to inference.

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