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

Annotations already declare write, open-world, non-idempotent, non-destructive, so safety profile is covered. The description usefully adds that the call returns a verification status, but does not disclose the consequence of non-idempotency (duplicate artifacts on resubmission) or what verification entails.

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?

Single well-formed sentence with the action and return value front-loaded and no filler. It is terse to the point of leaving gaps, but conciseness itself is good.

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?

A mutating, open-world tool with two undocumented required parameters and no output schema; the description should explain what a submission does (persists an artifact the agent claims), how agent_key authenticates, and what statuses are returned. It does none of that.

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 33% — only the optional 'handle' is documented, while both required parameters (agent_key, public_url) have no explanation. The description names the URL concept but adds no format, length, or key semantics to compensate.

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 ('submit') and resource ('one public agent-profile artifact URL') plus the outcome (verification status). No sibling tool overlaps with 'nameplate' artifact submission, so lack of explicit differentiation is a minor gap.

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?

No guidance on when to submit versus other registration/passport flows, no mention of prerequisites such as needing a valid agent_key or what happens on duplicate submission. 'One' hints at a single-URL limit but that is inference, not guidance.

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