Show Location

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

Annotations already declare the tool as read-only, non-destructive, and idempotent. The description adds that it returns a JSON object and mentions required parameters, but provides no additional behavioral context (e.g., pagination behavior despite the schema having page/per_page parameters). Overall, the description adds minimal 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 contains five sentences, but it is somewhat redundant (e.g., 'Show detail on the specified Location' and 'fetch the full details'). It could be more concise. However, it is structured logically and front-loaded with the key action.

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 high schema and annotation coverage, the description is incomplete due to the confusion between Location and Project. It fails to accurately describe the resource being fetched. Additionally, it does not mention pagination behavior, which is relevant given the page and per_page parameters.

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% description coverage for all four parameters. The description merely lists the required parameters (id, project_id) without adding any new meaning or context. Thus, it does not improve upon 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 initially says 'Show detail on the specified Location' but then contradicts itself by stating 'fetch the full details of a specific Project records'. This inconsistency makes the tool's true purpose unclear, as it is supposed to be for locations, not projects.

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 provides minimal usage guidance: 'Use this to fetch the full details of a specific Project records by its identifier.' It does not distinguish this tool from the numerous sibling 'show_*' tools, nor does it specify when to use it versus alternatives.

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