Show A Company Inspection Template Item Evidence Configuration

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that the tool returns a paginated JSON array with metadata, but does not disclose any additional behavioral traits such as rate limits, authentication requirements, or side effects.

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 6 sentences and front-loads the purpose. It includes the API version and endpoint, which may be extraneous for an AI agent but not overly verbose. Could be trimmed slightly without losing clarity.

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 no output schema, the description explains the return format (paginated JSON array of Inspections with metadata) and pagination parameters. It covers required fields and the endpoint. However, it does not define 'evidence configuration' or its relationship to inspections, which might be useful context.

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 has 100% coverage with descriptions for all 4 parameters. The description only restates required parameters and pagination details, not adding significant new meaning 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 states 'Show the specified Company Inspection Template Item Evidence Configuration' and provides the endpoint, clearly indicating the specific resource. However, it confusingly says 'fetch the full details of a specific Inspections' which seems to conflate the evidence configuration with inspections themselves.

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 the user to use this tool to fetch full details but does not contrast with siblings like 'show_a_project_inspection_template_item_evidence_configuration' or indicate when to prefer one over the other. No 'when not to use' guidance is provided.

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