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

readOnlyHint=true already establishes the safe-read profile, but the description adds substantial context beyond annotations: it explains the route field values (review, known_owner, auto_branch, rename), the owner_runs linkage, and what the warnings refer to. With no output schema, this return-shape disclosure is genuinely valuable.

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?

Front-loaded with the audience restriction, then the resource, then a dense route-by-route explanation. The route detail is long but each clause carries distinct meaning since there is no output schema to fall back on.

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?

With no output schema, the description adequately covers the returned structure (route meanings, owner contacts, warnings, rename.from/to). The remaining gap is the status filter and any pagination/ordering behavior, which an agent might still need.

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 single 'status' parameter has 0% schema description coverage, and the description does not explain what the filter does or how the enum values behave. It only references 'status approved' incidentally while explaining the auto_branch route, which is not enough to compensate for the coverage 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?

States a specific resource ('Queue of business applications with owner contacts and warnings') and scopes it with 'Only for the Awning team.' It is clearly distinguishable as the read-side counterpart to op_decide_application, though it never names that sibling explicitly.

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 'Only for the Awning team' clause gives an audience restriction, which implies when it is appropriate. However it never names alternatives such as op_decide_application or op_businesses, nor states when not to use it, so routing is left to inference.

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