ps_scale

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

No annotations are provided, so the description carries full burden. It mentions the tool 'handles dyno scaling with support for type-specific adjustments', which hints at mutation behavior, but lacks details on permissions, rate limits, or what happens to existing dynos. It partially discloses behavior but leaves gaps for a mutation tool.

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 front-loaded with the core purpose, followed by bullet-like usage points, and ends with a summary sentence. Every sentence adds value without redundancy, making it efficient and well-structured.

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 no annotations and no output schema, the description covers purpose and usage well but lacks details on behavioral traits like error handling or return values. For a mutation tool with two parameters, it's adequate but has clear gaps in completeness.

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 schema already documents both parameters. The description adds context by mentioning 'type-specific adjustments' and viewing current formation, which aligns with the dyno parameter's optional nature, but does not provide additional syntax or format details 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?

The description clearly states the verb ('Scale and resize') and resource ('Heroku application dynos'), with specific actions like adjusting quantities, changing sizes, viewing details, and managing allocation. It distinguishes from siblings like ps_list (which likely lists dynos) and ps_restart (which restarts them).

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 explicit usage scenarios (e.g., adjusting dyno quantities, changing sizes, viewing details), but does not specify when NOT to use it or name alternatives among siblings. It implies usage context but lacks exclusions like 'use ps_list for just listing without scaling'.

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