attest-mcp-server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's action ('Reject', 'changes the approval status'), outcome ('returns the final rejected state'), and system impact ('in Attest'), though it lacks details on permissions, error handling, or side effects. No contradiction exists.

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 concise and well-structured, with two sentences that front-load the core action and usage context. Every sentence adds value: the first defines purpose and key constraint, the second provides usage guidelines and outcome. No wasted words.

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 the tool's complexity (a mutation with no annotations or output schema), the description is fairly complete. It covers purpose, usage, and behavioral outcome, but lacks details on error cases, permissions, or return format specifics. It compensates well for the absence of structured fields but has minor gaps.

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%, so the schema already documents the 'challenge_id' parameter fully. The description does not add any additional semantic context about the parameter beyond what the schema provides, such as format examples or sourcing. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 clearly states the tool's purpose with specific verbs ('Reject', 'changes the approval status') and resource ('pending approval challenge'), distinguishing it from sibling tools like 'grant_approval' (approve) and 'get_approval' (inspect). It explicitly mentions what it does not do ('without minting a child credential'), adding precision.

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?

The description provides explicit guidance on when to use this tool ('when a human declines the requested access') and when not to ('for passive inspection use get_approval instead'), naming a direct alternative. This helps the agent choose correctly between active rejection and passive inspection.

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