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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context: ordering (newest first), page size (up to 100), project scoping, and the Cotlet API key auth requirement. It does not describe return format beyond the field list, which is a minor gap for a tool with no output schema.

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?

Five short sentences, front-loaded with what the tool returns, then narrowing to ordering, filtering, pagination, and auth. No sentence is wasted, though the status explanation is slightly redundant with the schema field description.

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?

With no output schema, the description carries the return-value burden and mostly does so by naming the key fields. Combined with ordering, page size, project filter, and the auth requirement, an agent has enough to call it correctly; only the raw response envelope and pagination token handling are unspecified.

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 description coverage is 100%, so the baseline is 3. The description largely restates schema content ('Status is the label Contractor Foreman shows, for example draft or approved' mirrors the status field description) and adds only the page-size tie-in for limit. It does not add format or syntax beyond 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?

States a specific verb (list) and resource (estimates) and enumerates the fields returned: status, total, and whether the client opened or signed them. Within the contractor-foreman family the alternatives (create_estimate, send_estimate) are clearly distinct operations, so an agent can route without opening the schema.

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?

'Optionally for one project' implies you can scope the list, but there is no explicit when-to-use guidance, no mention of alternatives like get_project for a single project's context, and no stated prerequisites beyond the API key. Usage is inferrable rather than stated.

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