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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds the authentication requirement ('Requires your API key') and specifies the return payload (status and every section draft), which provides behavioral context beyond the annotations.

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?

The description is two sentences with no filler. The primary purpose and scope are front-loaded, and the API key requirement is a brief, necessary addition. Every word earns its place.

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?

Given the simple tool with two optional parameters and no output schema, the description covers the essential details: what it returns, how to identify the application, and the auth requirement. It does not explicitly note that at least one identifier must be provided (schema lists both as optional), but the phrasing 'by application_id or grant_id' implies this, so the gap is minor.

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 descriptions for both parameters are complete (100% coverage), but the description clarifies that application_id and grant_id are alternative identifiers for the same application, which is not explicitly stated in the schema. This adds relational meaning beyond the individual parameter descriptions.

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 clearly states the verb 'Fetch', the resource 'YOUR grant applications', and specifies it returns 'status + every section draft'. It distinguishes from siblings like get_grant (generic grant info) and list_my_applications (listing all) by emphasizing it retrieves a single application belonging to the caller.

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 description implies usage when you need a specific application, but it does not explicitly mention alternatives like list_my_applications for all or get_grant for general grant details. No explicit when-not or alternative routing is provided, so usage context is only implied.

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