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

Annotations already flag this as non-read-only, destructive, and idempotent; the description adds valuable context they cannot carry: the required auth scope and plan tier, plus the side effect that the note is appended to the application's tracker card. It does not explain why the operation is marked destructive (e.g. whether archiving hides the application) or how the note interacts with an existing 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?

Two sentences, front-loaded with the mutation and its allowed values, followed by the side effect and prerequisites. No filler or repetition of the title.

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 three-parameter idempotent mutation with no output schema, the description covers purpose, allowed values, side effect, and authorization requirements. Minor gaps remain around what 'destructive' means in practice and what the call returns on success.

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 0%, so the description must compensate. It does add real meaning for 'note' (optional, appended to the tracker card) and confirms the status enum members, but it leaves applicationId unexplained and doesn't say whether the note is appended to or replaces prior notes, so half the parameter semantics remain schema-only.

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?

Names a specific verb (sets) and resource (application status), enumerates the three permitted status values, and explicitly marks the excluded state '(not submitted)', which implicitly routes submission to the sibling getfund_submit_application. The tracker-card note effect is also stated.

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 '(not submitted)' parenthetical and the prerequisite line (applications:write scope plus the Autopilot plan) tell the agent the conditions for a successful call. It stops short of naming getfund_submit_application as the alternative for actually submitting, so the routing is inferential rather than explicit.

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