twprojects-list_project_budgets

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

Annotations already indicate readOnlyHint=true, consistent with the list operation. Description adds that budgets are 'top-level project financial budgets' and filtering options, but no additional behavioral details like pagination or response format beyond what schema provides.

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?

Single sentence, front-loaded with purpose, no superfluous words. Efficient and clear.

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?

Description covers core purpose and filters. With output schema present, return values are documented elsewhere. Could mention pagination or verbose mode briefly, but overall adequate.

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 coverage is 100%, so baseline is 3. Description mentions filters but does not add semantic meaning beyond schema descriptions. No new insights on parameter usage or format.

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 lists project budgets and distinguishes them as 'top-level project financial budgets', differentiating from sibling tool 'twprojects-list_tasklist_budgets'. The verb 'List' and resource 'project budgets' are specific.

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?

Description mentions filtering by project_ids or status, giving clear use cases. However, it does not explicitly state when not to use this tool or compare with alternatives like 'twprojects-list_tasklist_budgets'.

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