emu_get_evidence

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

No annotations are provided, so the description must carry the full behavioral burden. 'Fetch' implies a read operation, but the description does not disclose whether fetching can generate state, whether it is idempotent, whether a call session must already exist, or what the returned evidence bundle contains.

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 a single, front-loaded sentence with no filler or repetition. It is concise, though it sacrifices useful behavioral and usage detail for brevity.

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, no output schema, and an ambiguous 'id' parameter, the description is not complete enough. It does not explain how the evidence bundle is obtained, what data it contains, how errors surface, or how this tool relates relation to the evidence creation workflow.

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 required parameter is only an 'id' string with 0% schema description coverage. The description vaguely suggests the id relates to a 'canonical call session', but it does not clarify whether id is a session id, an evidence bundle id, or something else, leaving the parameter ambiguous.

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 identifies a specific action ('Fetch') and resource ('evidence bundle') with a qualifier ('canonical call session'). It distinguishes from emu_create_evidence_bundle and emu_get_call_session, though 'canonical' is left undefined and could confuse an agent.

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 guidance about when to use this tool versus alternatives, no prerequisites, and no mention of whether the caller needs to create a session or evidence bundle first. The agent must infer usage from the name and description.

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