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

Annotations cover the safety profile (not read-only, not destructive, closed-world), and the description adds real context beyond them: the record is stored as 'pending', it is reviewed before listing/ranking, and ranking cannot be bought. It stops short of stating permissions, idempotency, or what happens on a duplicate submission.

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 first sentence and the field list are front-loaded and useful, but the three trailing sentences about evidence-based ranking are policy copy that does not help an agent invoke the tool correctly. The description also omits user_request while enumerating the other fields.

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?

With 7 parameters, 6 required, no output schema, and no enums, the description covers most of the surface but never mentions the user_request field, and says nothing about the response or what a caller should do after a successful store. Adequate but with a clear gap.

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 100%, so all seven parameters are already documented, including the 'no street address or phone number' constraint on location. The description restates the field list rather than adding format or syntax detail beyond the schema, so the baseline 3 applies.

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 and resource: 'Store a pending agency application.' The 'pending' qualifier and the review framing distinguish it from read-only siblings like get_agency and search_agencies, so an agent knows this is the submission path.

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 gives clear context (a pending application subject to evidence review) and an explicit field-level exclusion: 'Do not collect a phone number or street address.' It does not name a sibling or state an explicit when-not beyond that, so it falls short of a 5.

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