List Company WBS Patterns

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds that it 'Returns a paginated JSON array of Work Breakdown Structure records' and mentions pagination metadata, providing useful behavioral context beyond the annotations.

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 concise with 3 sentences, each adding unique information. It is front-loaded with the purpose and includes essential details like required parameters, pagination, and API reference. No unnecessary 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 the excellent annotations and full schema coverage, the description is fully complete. It explains the tool's output format, pagination behavior, and required parameter. No output schema exists, but the description mentions pagination metadata, which suffices for a list operation.

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?

Input schema covers all 3 parameters with descriptions (100% coverage). The description adds usage guidance for pagination: 'Use page and per_page to control pagination; the response includes pagination metadata.' This adds value beyond the schema's default values.

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 the purpose: listing all WBS patterns for a given company. It specifies the resource ('Work Breakdown Structure records'), the action ('enumerate'), and the use cases (paginated overview, find IDs, filter). This differentiates it from sibling list tools that target other entities.

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 tells when to use the tool: 'when you need a paginated overview, to find IDs, or to filter by query parameters.' It also mentions the required parameter company_id. However, it does not explicitly state when not to use it or mention alternative tools for different scopes.

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