pin.analyze

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

Annotations already declare readOnly, non-destructive, and idempotent behavior, so the safety profile is covered. The description adds a stylistic note ('Decision evidence—not a dump') hinting at concise output, but it doesn't disclose how the three modes are triggered or whether outputs are structured.

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 very brief (around 15 words), which is economical, but the content is cryptic and uses jargon without context. The list structure is confusing and not front-loaded with a clear action statement.

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?

There is no output schema, so the description must explain return values. The phrase 'Decision evidence—not a dump' is too vague, and the tool supports multiple modes without describing what each mode returns or how they differ.

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?

With an empty schema, the description must explain what context or implicit inputs are needed, but it only mentions 'evidenceSetId' without elaboration and lists three modes with no way to select them. This leaves the agent guessing how to invoke the tool.

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 lists three capabilities ('EvidenceBrief (knownFacts/gaps/evidenceSetId), documentation gaps, or coverage compare') but never states a clear verb or resource. The name 'analyze' is generic, and it overlaps with sibling pin.compare for coverage comparison, making it unclear what uniquely identifies this tool.

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?

There is no explicit when-to-use guidance, no mention of alternatives, and no exclusions. Siblings like pin.compare, pin.prove, and pin.verify suggest overlapping functions, but the description doesn't clarify boundaries or contexts.

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