gorelo_get_contract

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read. The description adds genuine value by disclosing that the response expands into products and labor per service line, which matters given there is no output schema. It says nothing about not-found behavior or permission requirements, so it is useful but not rich.

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?

One sentence that front-loads the action and resource, then adds the payload detail. Zero redundancy or filler.

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?

For a one-parameter read tool with a fully documented schema and a readOnly annotation, the description covers both what it does and what comes back (products, labor, service lines), which compensates for the absent output schema. Only minor gaps remain around error/empty-result handling.

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?

Single parameter with 100% schema description coverage ('Identifier of the contract'), so the schema carries parameter semantics. The description adds no format, sourcing, or validation hints for contractId, making the baseline 3 appropriate.

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?

Specific verb + resource ('Gets one contract') with added scope detail about what the payload expands into. The singular 'one contract' implicitly distinguishes it from gorelo_list_contracts, but the sibling is never named, so an agent must infer the pairing.

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?

Usage is only implied: the singular phrasing suggests fetching a known contract ID while gorelo_list_contracts handles discovery. There is no explicit statement of when to prefer this tool, no prerequisite that contractId comes from the list endpoint, and no exclusions.

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