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

The description discloses that the records are not BTW-verified operating capacity, which is a behavioral trait. However, with no annotations provided, additional transparency about permissions, side effects, or data freshness would be helpful. The description partially addresses 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?

The description consists of two concise sentences that are front-loaded with the core purpose. It is efficient and avoids unnecessary detail.

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?

Given the tool has two parameters with no schema descriptions, no output schema, and no annotations, the description is insufficient to fully understand how to use the tool. It lacks parameter documentation and output format details.

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 description does not mention either parameter (limit, state). With schema description coverage at 0%, the description should provide meaning for these parameters, but it offers none. This is a significant 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?

The description clearly states the tool retrieves a 'project pipeline' that is separately classified and third-party reported, distinguishing it from sibling tools that focus on dataset summaries and facilities. However, the term 'project pipeline' is somewhat vague and could benefit from more specificity.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. Agents would have to infer usage context from the tool name and sibling names alone.

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