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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the description adds real value by scoping the result (owner-created grants and remaining caps) and by disclosing an authorization boundary agents cannot cross. It does not describe return shape or ordering, but the broader safety profile is covered.

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?

Two short sentences with no filler; the operation comes first and the constraint second. Every clause carries information an agent could act 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?

For a zero-argument read tool with full annotation coverage, the description gives enough to select and invoke it: what is returned at a high level and what cannot be done. Without an output schema, more detail on the shape of 'grant' and 'caps' records would help, but the essential calling information is present.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for a parameterless schema applies. The description correctly implies the scope is fixed to the calling client rather than selectable.

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 verb (read) and resource (owner-created standing grants plus remaining caps), which is clearly distinct from all listed siblings, none of which touch grants. Slightly less crisp because 'this client's' implies context the agent must already hold, and the second sentence restates a permission boundary rather than the operation.

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?

'Read this client's ... grants' indicates a read-only listing use case, and the exclusion 'Agents cannot create or widen grants' rules out a mutation path. However, no alternative tool is named and no condition is given for when an agent should call this versus other inspection endpoints.

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