Api contracts currency retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description needs only to add what the annotations don't say. Instead it says the endpoint allows contracts to be 'viewed or edited', implying write capability that conflicts with the read-only annotation, and offers no other behavioral context.

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?

It is a single short sentence, so nothing is bloated, but the sentence is generic auto-generated text rather than a front-loaded statement of the actual purpose. Brevity without information is not a strength.

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?

There is no output schema, so the description is the only place an agent could learn what this endpoint returns, and it says nothing about the currency payload. For a zero-param retrieve with no documented response, the description is materially incomplete.

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 tool takes zero parameters and schema coverage is 100%, so there is nothing for the description to clarify at the parameter level. Baseline 4 applies.

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 is generic boilerplate ('API endpoint that allows contracts to be viewed or edited') that does not actually state what this specific endpoint returns. The tool name implies a currency lookup for contracts, but the description never mentions currency or what is retrieved, so an agent cannot distinguish it from contracts_retrieve or contracts_status_retrieve.

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?

There is no indication of when to call this tool, no mention of alternatives such as contracts_retrieve, entities_currency_retrieve, or pmbok_projects_currencies_retrieve, and no prerequisites. Usage must be inferred entirely from the name.

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