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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds meaningful context by stating it contains no token, secret or permission to send — telling the agent this cannot be used to authenticate or authorize a send. It does not address return format, but that is a minor add.

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, front-loaded with the operation and its scope, with the security clarification in the second sentence. No filler text.

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, annotated read tool with no output schema, the definition covers what it returns (a client ID) and that it is not a credential. The only gap is that 'owner-created grant setup' is jargon left unexplained, leaving the agent to guess the downstream workflow.

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 the schema carries the full parameter burden and there is nothing further the description could add. Baseline 4 applies for a no-parameter tool.

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?

A concrete verb ('Read') and a concrete resource ('your own client ID') make the operation unambiguous, and the reference to grant setup hints at the related list_agent_grants workflow. It stops short of a full sibling differentiation, but the core purpose is clear.

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?

'for owner-created grant setup' implies the context in which to call it, but there is no explicit statement of when not to use it or which sibling tool (e.g., list_agent_grants) covers adjacent needs. Usage must be inferred from a single conditional phrase.

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