get_estimate

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description's one contribution beyond them is the access constraint (only session-owned documents), which is useful but is the entire behavioral content; nothing is said about failure behavior for non-owned IDs or about the returned payload. No contradiction with the annotations, though the session-scoping sits somewhat oddly beside openWorldHint=true.

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?

A single short sentence with no padding, and the access constraint is front-loaded. However, the terseness crosses into under-specification rather than efficient density for a tool that has an opaque required identifier.

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 single-lookup read tool with rich annotations this could be nearly complete, but there is no output schema, so the description should hint at what is returned (full estimate document?) and where estimateId comes from. Neither is present, so an agent must guess at both input provenance and return content.

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?

There is one parameter (estimateId) with 0% schema description coverage; only a regex pattern is given. The description does not say what the ID identifies, where an agent obtains it, or what happens if it references another session's document, so it fails to compensate for the coverage gap.

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?

"Read only a document owned by this session" states a verb (read) and a generic object (document), but never names the resource as an estimate; the resource is only recoverable from the tool name. It does not distinguish this from the many sibling getters (get_application, get_catalog, get_calendar), leaving the agent to infer that this one retrieves estimates.

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 only usage signal is the scope constraint that the document must be owned by this session, which implies a precondition but not when to prefer this tool over siblings. No alternatives are named and no exclusion (e.g., unowned/shared estimates) is spelled out.

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