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

With no annotations, the description carries the transparency burden. It does add meaningful context: the permission scope required and the fields found in the full content. However, it doesn't disclose error behavior, response format, or explicitly state that this is a read-only operation. The term 'Get' implies read-only, but more explicit disclosure would be better given the absent annotations.

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 whole description is one well-formed sentence that front-loads the action and resource, then packs the field details and authentication requirement. Every word adds value, with no redundancy or filler.

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?

For a simple tool with a single parameter and no output schema, the description gives enough context via the field list and auth scope. It could be slightly more complete by clarifying returned structure or error cases, but given the tools rule set, it is close to sufficient.

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 input schema fully covers the single parameter 'id' with 'The report UUID.' The description's 'by id' only restates the schema, adding no new semantic detail. Schema description coverage is 100%, so the baseline of 3 is appropriate.

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 states the action and resource: 'Get the full structured content of one end-of-day report by id'. It also lists the report components (KPI status, shipped, silent, slipping, blockers), and the singular 'one...by id' differentiates it from the sibling tool list_reports.

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 conveys that this is for retrieving a single report by its id, and it mentions the 'reports:read' scope requirement. It does not explicitly name an alternative for listing reports, but the 'by id' phrasing gives a clear invocation context.

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