Start evidence session

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

No annotations provided; description explains side effect (creating directory) and path. Lacks details on permissions, idempotency, or failure modes, but covers basic behavior adequately.

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 with no wasted words. Front-loaded with action and resource, then return value and usage tips.

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?

Covers creation, return value, and links to siblings. Could elaborate on session purpose, but given schema coverage and output schema absence, it's sufficiently 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 covers both parameters with descriptions. Description adds value by clarifying baseUrl usage for url resolution, which is not obvious from schema alone. FeatureName explanation is minimal but acceptable.

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 it creates an evidence directory with specific path, returns sessionId, and relates to sibling tools. Verb 'creates' and resource 'evidence directory' are explicit.

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?

Indicates when to use (start session) and references sibling tools: 'Call finish_evidence_session when done' and 'pass to request'. No explicit when-not-to-use, but context suffices.

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