Get A Single Resource Planning Tag

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. Description adds value beyond annotations by specifying the endpoint, API category, and that it returns a JSON object. There is no contradiction with 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?

Four short sentences: purpose, usage, return type, required params plus endpoint. No wasted words, all information is pertinent and front-loaded.

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 covers purpose, usage, required params, and endpoint. However, it does not clarify that optional page/per_page parameters may have no effect on a single tag retrieval, nor does it explicitly state that only one record is returned.

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 baseline 3. Description adds context by listing required parameters and showing endpoint structure (path parameters). However, it does not explain the optional 'page' and 'per_page' parameters, which appear irrelevant for a single resource fetch.

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 verb ('Get') and resource ('Single Resource Planning Tag') and distinguishes from list/delete siblings by specifying 'single' and 'by its identifier'. However, it refers to 'Resource Planning records' which could be slightly ambiguous given it's a tag, not records.

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 when to use this tool ('fetch the full details of a specific... by its identifier') and lists required parameters. However, it does not explicitly exclude using it for multiple tags or mention alternative list endpoints (e.g., get_all_resource_planning_tag_for_a_company).

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