Show Project Insurance

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. The description adds no behavioral details beyond stating it returns a JSON object. It does not explain why pagination parameters (page, per_page) are present on a show endpoint, which could confuse agents.

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 relatively concise with four sentences covering purpose, usage, return type, and required parameters. Minor redundancy ('Return detailed information' and 'fetch the full details') but overall efficient and front-loaded.

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?

No output schema exists, so the description should explain the response structure, but it only says 'JSON object describing the requested Directory records.' It does not mention key fields or note that pagination parameters may be irrelevant for a single-item fetch, leaving important gaps.

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 100%, and the description merely repeats required parameters (project_id, id). No additional semantic value beyond what the schema already provides. The description does not clarify the purpose of optional parameters like view or pagination.

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 it returns detailed insurance information for a project, using 'Return detailed information on the specified Insurance' and 'fetch the full details'. It distinguishes from list or create tools. However, the phrase 'Directory records' introduces slight ambiguity since the tool is specifically about insurance.

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?

Lists required parameters but does not explicitly state when to use this tool versus list_project_insurances or other alternatives. No exclusions or context on when not to use it. The description implies single-record fetch but lacks comparative guidance.

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