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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds the auth prerequisite ('signed in to Awning') and the content shape of the response, but says nothing about rate limits, freshness, or what happens with multiple businesses beyond the schema note.

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?

Compact and front-loaded, leading with the audience constraint before listing the returned content. The final field list is slightly clipped/list-like but every clause conveys content not available elsewhere.

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 usefully enumerates what the response contains (business/application status, pending request count, pending_rename, unfinished draft), which is exactly what an agent needs. It could clarify behavior for multi-business owners and its relation to sibling status tools, but nothing critical is missing.

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% and the single parameter's only nuance ('only needed if you manage several businesses') is already in the schema, so the description adds no parameter meaning. Baseline 3 applies when the schema fully documents inputs.

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 names the resource (the owner's businesses and applications) and enumerates the specific status fields returned (pending requests count, pending_rename, unfinished draft), which is far more than a restatement of the title. It is clearly a read-status tool for a signed-in business owner, though it does not explicitly contrast itself with lookalike siblings such as op_applications or op_businesses.

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 phrase 'Only for business owners signed in to Awning' establishes the audience and prerequisite, which is genuine usage guidance. However, it never states when to pick this over op_applications, op_businesses, or my_profile, so routing still requires inference.

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