konsulto_attach_evidence

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

No annotations provided; description fully bears burden. Discloses that exactly one of three content sources must be set, returns evidenceId, and does not link to findings. Lacks size limits or error behavior, but sufficient for safe use.

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?

Three focused sentences: action+return, sibling usage, constraint. No wasted words, front-loads purpose.

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 no annotations or output schema, description covers purpose, return, sibling links, input constraint, and default filename. Could add size limit or error info, but overall complete for decision-making.

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 83% of parameters with descriptions. Description adds the critical one-of constraint and default filename behavior not in schema. Adds meaning beyond schema without redundancy.

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?

Clearly states it uploads a file or inline content as an attachment, returns evidenceId, and distinguishes from linking tools. Verb 'upload' with specific resource 'attachment in active audit'.

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 tells agent to pass evidenceId to konsulto_add_evidence_to_finding or include in konsulto_compose_finding's evidence array. Also states 'does NOT link to a finding by itself', precluding misuse.

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