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

Annotations already declare the safe read-only, non-destructive, closed-world profile, so the bar is lower. The description still adds real value beyond that: the output is 'redacted' and the call requires a specific credential (an opaque application grant passed as an Authorization bearer, explicitly not a Firebase ID token), which is exactly the kind of auth context annotations cannot convey.

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, purpose front-loaded, no filler. The token caveat is slightly repetitive of the schema wording, but nothing is wasted overall.

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?

An output schema exists, so return values need not be explained, and the auth requirement is covered. What is missing is any meaning for applicationId (where it comes from, what an invalid/expired grant yields), leaving a gap for a tool whose only failure mode is likely a bad credential.

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 coverage is 50%: AgentGrant is already documented in the schema (with the same 'not a Firebase ID token' point, so the description is largely redundant there), while applicationId has no description in either place. The description compensates for neither the undocumented applicationId nor adds format detail, so it sits at the baseline.

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 states a specific verb and resource ('Read redacted application status'), which is clear and unambiguous. However, it does nothing to distinguish this tool from its siblings (prepare_application, get_formation_contract, etc.), leaving the agent to infer that this is the status-read path rather than an alternative to them.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named or excluded. Usage is only weakly implied by the word 'status' — the agent gets no criteria for choosing this over prepare_application or get_formation_contract.

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