Show Manpower Logs

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it returns a JSON object and includes the Procore API endpoint details. It does not disclose additional behavioral traits like authentication requirements or rate limits, but annotations cover safety.

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 (under 100 words), front-loaded with the purpose, and structured with clear sentences. It includes endpoint and required params without unnecessary fluff.

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?

Despite no output schema, the description only vaguely mentions 'Returns a JSON object describing the requested Daily Log records'. It does not detail return fields or explain why pagination params (page, per_page) are present in schema for a single resource endpoint. Completeness is lacking for an AI agent to fully understand behavior.

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%, so the baseline is 3. The description mentions required parameters (project_id, id) but does not add meaning beyond the schema. It does not explain optional params page/per_page, which are described in 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 it returns a single Manpower Log and fetches full details of a specific Daily Log records by identifier. The title and name align. Although it does not explicitly distinguish from sibling 'list_manpower_logs', the word 'single' implies it is for a specific log, not listing.

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 says 'Use this to fetch the full details of a specific Daily Log records by its identifier', which gives context for when to use it (when you have an ID). However, it does not mention when not to use it or compare with alternatives like 'list_manpower_logs'.

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