get_orchestration_policy

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

The word 'Read' implies a non-mutating operation, and there are no annotations to contradict that, but the description does not disclose return format, error behavior, or whether any side effects occur. Since no annotations are present, the description alone carries this burden.

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 two short sentences and gets to the point quickly. No unnecessary detail or repetition.

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?

For a simple read operation, the description is mostly sufficient, but it omits parameter semantics and does not mention what the response contains. This leaves minor but real gaps for a caller.

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 one parameter, agent_name, but the description does not explain its meaning or expected values. The title and default value provide only minimal hints, leaving the parameter underspecified.

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?

States a specific action ('Read automatic delegation policy') and identifies the resource, so the core purpose is clear. The phrase 'or offer it' is slightly ambiguous but does not obscure the main function.

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?

Provides a usage cue ('Call when deciding whether to delegate or offer it') but does not explicitly state when not to use it or name alternative tools. Sibling tools like delegate_task and route_task exist, yet the description does not contrast with them.

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