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

With no annotations provided, the description carries the full behavioral burden, yet it discloses little beyond the action. 'Return its verification status' hints at a synchronous verification response, but it omits whether submission is idempotent, what determines success/failure, permission requirements, or what happens to a previously submitted artifact. This is thin for a mutation-style tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler. It is efficient, though arguably under-specified rather than genuinely concise given the tool's complexity.

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 submission tool with no annotations, no output schema, and 67% of parameters undocumented, the description leaves major gaps: the meaning of 'verification status', auth expectations, and the required agent_key are all unaddressed. It is not complete enough for an agent to call it 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 33% - just the optional 'handle' param is documented, while the two required params (public_url, agent_key) are bare. The description clarifies that the URL is a 'public agent-profile artifact URL', adding marginal meaning for public_url, but says nothing about agent_key or how handle interacts with it. It fails to compensate for the low coverage.

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: 'Submit one public agent-profile artifact URL'. The agent knows exactly what action is taken. However, it offers no differentiation from the numerous sibling submission tools such as submission_post, submission_candidate_get, or submission_reject, leaving the agent to guess which submission flow this belongs to.

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?

There is no when-to-use guidance, no prerequisites, and no named alternatives. The only implicit signal is the word 'one' (single URL), which hints at a per-artifact scope but is not framed as usage guidance.

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