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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It does not say whether the scan is read-only, whether the repository is cloned or fetched over the network, whether there are rate limits or permissions requirements, or what the generated badge actually is (a URL, a Markdown snippet, a file). Only the phrase 'dynamic verified Markdown shield badge' hints at side effects.

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 the action stated first and the output mentioned second; almost every word earns its place. The adjectives 'dynamic verified' are slightly promotional but do convey that the badge reflects scan results.

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 one-parameter tool with no output schema and no annotations, an agent still needs to know what comes back from the scan and how the badge is delivered. The description signals a scan result and a badge but leaves the return shape and side effects unspecified.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines the repo slug/URL format and the baseline is 3. The description adds no further meaning about the parameter, and it slightly widens the scope by mentioning MCP servers even though the only parameter described is a GitHub repo slug or URL.

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 names a specific verb and resource ('Scan any GitHub repository or MCP server for prompt-injection vulnerabilities') and adds the side effect of producing a shield badge. It is clear what the tool does, though the pairing of a scan with badge generation makes the primary output mildly ambiguous.

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 guidance on when to use this versus anything else, no prerequisites (public vs private repos, whether authentication is needed), and no mention of when not to use it. The agent must infer all of this from a single sentence.

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