check_trust_tier

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

Describes outputs (trust score, tier, rate limits, JWS) and states no authentication. However, with no annotations, the description could better disclose caching behavior (force parameter hints at it) and whether the operation is idempotent.

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?

Two sentences, no redundant information, front-loaded with purpose and outputs. Highly efficient.

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?

Given no output schema, the description enumerates return values well. It lacks details on error handling for missing repos, but overall provides sufficient context for an agent to invoke the tool.

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 covers all three parameters with descriptions. The tool description adds no additional meaning beyond what the schema provides, resulting in a baseline score.

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?

Description clearly states the tool scans a GitHub repository and returns trust tier, rate limits, and attestation. It distinguishes from siblings like 'check_security' and 'verify_trust' by specifying the use case of checking any tool or agent before running.

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?

Explicitly says 'No authentication required' and 'Use this to check any tool or agent before running it.' This provides clear when-to-use context, but does not explicitly exclude scenarios where alternatives might be better.

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