read_announcement

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds value by stating the tool returns the full text rather than a summary, but it does not describe response shape or edge cases. This is adequate but not richly transparent beyond the 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?

One short sentence, front-loaded with the core purpose ('Full text of one announcement'), and the id provenance is appended efficiently. No wasted words.

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 single-parameter read-only tool, the description gives all necessary calling context: what the tool returns, where the id comes from, and that it is read-only via annotations. The lack of an output schema is acceptable because the description already states the result is the announcement's full text.

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 coverage is 0%, yet the description compensates fully by explaining that the parameter is the numeric id coming from list_announcements, and clarifies the string-typed field is expected to carry a numeric value. This is exactly the kind of semantic bridge an agent needs.

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 uses a specific verb and resource: reads the full text of one announcement. It distinguishes itself from the sibling list_announcements by emphasizing 'one announcement' with 'full text', and even specifies the id source, so an agent can tell exactly what this tool is for.

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 clearly implies usage after list_announcements has provided the announcement id, and it clarifies this tool is for retrieving full text rather than listing. It does not explicitly state when not to use it, but for a simple single-id read tool the context is sufficiently clear.

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