bind_parse_credential

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly states the crucial nuance that signature verification is not performed, and it describes the output components. It does not mention error handling or side effects, but for a parse/inspect tool this covers the main behavioral trait.

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 two sentences, front-loaded with the core action, and contains no fluff. Every word earns its place, clearly stating what the tool does and when to use it.

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 simplicity (one parameter, no output schema), the description adequately covers the essential context: what it decodes, the fact it does not verify, and its intended purpose. It could specify the exact return structure, but naming 'header, payload, and signature' gives sufficient shape for an agent.

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 already provides 100% coverage with a single parameter `jwt` described as 'The VC-JWT string to parse'. The tool description adds no additional parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate.

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 uses the specific verb 'Decode' with the resource 'Bind Protocol VC-JWT' and explicitly states the output components (header, payload, signature). It clearly distinguishes itself from siblings by noting it does 'without verifying the signature' and frames it for inspection before verification.

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?

It provides explicit guidance on when to use the tool ('Use this to inspect a credential before verification') and implies a limitation ('without verifying'). However, it does not name alternative tools directly; the sibling context helps but the description itself stops short of explicitly saying 'use bind_verify_credential for verification.'

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