Show An Equipment Log

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it returns a JSON object and specifies the HTTP method and endpoint path. It does not disclose rate limits, authentication requirements, or other behavioral nuances beyond what annotations convey, so value added is moderate.

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 four sentences plus endpoint details. It is reasonably concise but includes some redundancy (e.g., repeating 'Field Productivity records') and extra context (API info) that may not be essential for an AI agent. Still efficient overall.

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 simple retrieval tool with 4 parameters, annotations, and no output schema, the description covers the core purpose, required params, and return type. It does not explain optional pagination parameters, but those are documented in the schema. Lacks a note about the response structure beyond 'JSON object', but that is adequate.

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?

The input schema has 100% coverage with descriptions for all parameters. The description reiterates 'Required parameters: id, company_id' and shows the URL pattern, but this only reinforces schema information without adding new meaning. Baseline 3 is appropriate.

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 explicitly states the verb ('Return detailed information about a specific equipment log'), identifies the resource ('equipment log'), and indicates it operates on a single resource by identifier. It clearly distinguishes from list tools by focusing on 'specific' and 'full details'.

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 advises to use this tool when fetching full details by identifier. Although it does not explicitly mention when not to use or list alternative tools, the context of sibling tools (e.g., 'list_all_equipment_logs') provides implicit guidance. The mention of 'required parameters' also hints at the prerequisite.

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