stratverity_get_badge

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

With no annotations provided, the description carries the full burden. It only states that a badge URL is generated, but discloses nothing else—no side effects, authentication needs, return format, or what the URL represents. This is a significant gap for an action that produces an artifact.

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 description is a single short sentence, which is concise. However, 'concise' does not mean 'empty': the sentence is so terse that it fails to convey any meaningful detail, borderlining on under-specification rather than efficient communication.

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 three parameters, no output schema, and no annotations, this description is woefully incomplete. It does not explain how the badge URL is constructed, what status values imply, or what the caller can expect in return. An agent would have no idea how to correctly use the parameters.

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?

The input schema has 0% description coverage for its three parameters (audit_id, score, status). The description only implies the role of audit_id via 'for an audit' but does not clarify the meaning or valid combinations of score and status. It adds almost no value beyond the schema's bare property names.

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 states a clear verb ('Generate') and resource ('badge URL for an audit'). It is specific enough to understand the tool's primary function, though it does not differentiate it from the siblings beyond a general sense of generating output.

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 is provided on when to use this tool versus stratverity_quick_check or stratverity_verify_hash. There is no mention of context, prerequisites, or alternatives.

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