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

Annotations already declare the tool is read-only, idempotent, non-destructive and closed-world, so the safety profile is fully covered externally. The description adds that the user answers 6 checks and receives a credibility score, BS meter and verdict, which is useful output context but modest beyond what the schema/annotations imply.

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?

Three tight sentences that front-load the purpose and outcome before a minor promotional link. The external URL plug is slightly extraneous but overall the text is efficient and well-ordered.

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?

With no output schema, the description responsibly names the returned artifacts (credibility score, BS meter, verdict) and the six-check input model. Combined with 100% schema coverage this is complete enough for an agent to call it correctly, though it could say a bit more about how the score is produced.

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 100% and every parameter carries an enum plus a description and weight, so the schema fully documents inputs. The description itself adds no parameter-level meaning beyond the schema, making the baseline 3 correct.

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 ('Score') and resource ('agency pitch') and clarifies the criterion of interest (real verifiable outcomes vs vanity metrics), which is a distinct purpose. It does not, however, differentiate itself from the many other *_grader / scorecard siblings such as gtm_audit_scorecard, so it lands at 4 rather than 5.

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?

'before you sign anything' implies the situation of use (evaluating a pitch ahead of commitment), giving implied timing guidance. There is no explicit statement of when NOT to use it and no named alternative tools, so it stays at the minimum-viable level.

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