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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Detailed info' without explaining error behavior (e.g., not found), permissions, rate limits, or the exact fields returned. For a read operation, it does not explicitly say it's read-only, which could be inferred but not disclosed.

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 sentence, front-loaded with the core purpose. It contains no redundant words or information. Every element is useful, making it highly concise and well-structured.

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?

The tool is simple (one parameter, no output schema), and the description conveys the basic operation. However, it lacks detail about the return format, error handling, or any other contextual information that would help an agent rely on it fully. It is adequate but has clear gaps, especially since no output schema exists to explain return values.

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 description coverage is 100% (the slug parameter is fully described with an example). The description repeats the slug concept but adds no additional meaning beyond what the schema already provides. Baseline of 3 applies since the schema does the heavy lifting.

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 indicates the tool returns detailed information about a single survey report, identified by slug. It distinguishes itself from sibling tools like 'search' and 'recommend_surveys' by focusing on a single report lookup. However, it lacks an explicit verb like 'get' or 'retrieve', though the name 'get_report' implies the action.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention when to prefer this over 'find_surveys_for_position' or 'search', nor does it state any exclusions or prerequisites. Usage is only implied by the 'by slug' qualifier, but there is no explicit context.

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