pangolinfo_capabilities

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

The description discloses that it has no backend call, is free, uses local data, and costs 0 points. It also describes the return structure. Since no annotations are provided, the description fully carries the transparency burden.

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 well-structured with bullet points and sections, but it is somewhat lengthy. It front-loads the purpose effectively, but some details could be trimmed without loss.

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?

Despite no output schema, the description clearly lists all return fields (version, locale, liveTools, workflows, tips). The parameter is fully explained. For a simple self-introspection tool, this is complete.

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 coverage is 100%, and the description adds significant context about the 'detail' parameter, explaining token usage and when to use each enum value, going beyond the schema.

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 it's a self-introspection tool that returns a full capability list, typical workflows, and usage tips. It distinguishes itself from sibling tools by focusing on overview rather than specific tool details.

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 specifies when to use (first connection, user asks 'what can you do', SOP planning) and when not to use (getting full description of a tool, checking balance). Also provides pairing advice with other tools.

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