Show Equipment Timecard Entry (Project)

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

Annotations already provide readOnlyHint=true, destructiveHint=false, etc. The description adds that it returns a JSON object and is a GET endpoint, which is useful context. No contradictions. It could mention error behavior or rate limits, but it adds value beyond 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 and well-structured: purpose, usage, required params, API info. However, it redundantly mentions 'Field Productivity records' twice and includes the full endpoint path, which is slightly verbose but not excessive.

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?

The description lacks details on the output structure (only says 'JSON object describing') and does not explain the optional pagination parameters (page, per_page) which seem unusual for a show endpoint. Overall adequate but incomplete without output schema.

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 coverage is 100% with all parameters described. The description only reiterates the required parameters without adding new meaning. Baseline of 3 is appropriate; it does not enhance understanding 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 clearly states the tool returns detailed information about a specific equipment timecard entry, using strong verb+resource ('Return detailed information'). It distinguishes from sibling tools like list, update, delete by specifying it fetches a single entry by ID. The JSON return type and required parameters are also mentioned.

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 explicitly says 'Use this to fetch the full details' and lists required parameters, guiding when to use. However, it does not provide explicit when-not-to-use or compare with alternatives like list, but the context is clear enough.

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