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

Annotations only cover the safety hints (readOnly=false, destructive=false, idempotent=false, openWorld=false); the description adds real pipeline context: static checks precede behavioral screening, verified arrivals follow the owner's approval policy while suspicious ones stay held, and the return is slug/status/static report with no guarantee of publication. It does not mention auth needs, cost beyond 'free', or rate limits, so not a 5.

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?

Four dense sentences, front-loaded with the operation and its pipeline, then the return semantics and prerequisite. No filler, though the metaphorical phrasing ('arrivals', 'screening') costs some clarity that plainer wording would not.

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 tool with 9 required params, a nested oneOf payload with three distinct submission kinds, low schema coverage, and no output schema, the description covers the process and return but says nothing about what shape of artifact to submit or how the kinds differ. An agent can call it, but not confidently.

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 only 30% across 10 parameters, yet the description never elaborates on name, tagline, story, creatorName, creatorContact, license, creatorSharePct, or the three-way 'spec' branch. It only gestures at agreementVersion and attestation; the oneOf spec variants (agent/mcp/mind) are entirely unexplained, so the description fails to compensate for the coverage gap.

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 frames the tool as a 'free declarative intake' that runs safety/screening steps and returns a saved slug/status, which tells an agent this is a write/submission operation distinct from the read-oriented siblings (get_resident, list_residents) and the transactional 'hire'. The verb is metaphorical ('surrender'/'arrivals') and the resource is never named plainly, so some inference is still required, but the operation is identifiable.

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?

It gives one prerequisite ('Read the surrender agreement and attest rights first') and implies when the tool applies (you have a spec to submit), but never states when NOT to use it or contrasts it with siblings such as hire. Guidance is implied rather than explicit.

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