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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds the ownership scope ('owned by the API-key account') which is useful context beyond annotations. However, it does not disclose pagination, filtering behavior, or return format, leaving some behavioral aspects undocumented.

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?

The description is a single sentence with no redundancy. The verb and resource are front-loaded, and the ownership scope is stated succinctly. It is appropriately sized for a simple list operation.

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 three parameters and no output schema, the description should provide at least some context on how to use the parameters or what to expect in the response. It does neither. The annotations cover safety, but the description is incomplete for an agent to make informed calls, especially with 0% schema description coverage.

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 schema has 0% description coverage, meaning the description must explain parameters but does not. None of the three parameters (limit, status, client_id) are mentioned in the description, leaving the agent without any semantic guidance beyond the schema's structural definitions.

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 action (List), the resource (consulting engagements), and the scope (owned by the API-key account). It is specific enough to distinguish from singular get_consulting_engagement and other list tools, though it does not name a sibling explicitly.

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 implies usage by its name and scope, but it provides no explicit guidance on when to prefer this over get_consulting_engagement or other list tools. No alternatives or exclusions are mentioned, so it relies on the agent inferring the intended use.

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