promote_governor

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

Without annotations, the description reveals that promoting consumes governor points, which is a key behavioral trait. However, it doesn't mention error conditions (e.g., insufficient points) or other side effects, leaving room for more transparency.

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?

Purpose is front-loaded in the first sentence. The Args section is bullet-like and efficient. Every sentence serves a purpose with no wasted words.

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?

Simple tool with 2 required params and no enums. Description covers how to obtain parameter values and a prerequisite (governor points). Output schema exists (per context signals) so return values don't need explanation. Adequate for the tool's complexity.

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 has no descriptions (0% coverage). The description compensates fully by explaining that 'governor_type' comes from get_governors output and 'promotion_type' from the same source, shown under each governor. This adds essential meaning beyond the schema's titles.

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?

Description clearly states 'Promote a governor with a new ability.' Verb 'promote' and resource 'governor' are specific, and the action is distinct from sibling tools like 'appoint_governor' or 'assign_governor'.

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?

Explicitly states requirement of governor points and directs user to 'get_governors' to see available promotions. Provides clear context for when to use, though no explicit when-not or alternatives beyond referencing sibling tool.

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