get_announcement

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the operation 'Get' (implying read-only) and lists return fields, but it does not address idempotency, error handling, required permissions, or performance characteristics. For a tool with no annotations, this is insufficient.

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 concise (three sections: purpose, args, returns) with no extraneous words. It front-loads the purpose and organizes details clearly. Every sentence adds value.

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 the low complexity (2 params, no nested objects, no output schema), the description covers the essential details: tool purpose, parameter semantics, and return structure. It lacks error handling or edge case info, but for a simple retrieval tool, it is largely complete.

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 has 0% description coverage, so the description must compensate. It adds meaning by labeling both parameters ('Canvas course ID' and 'Canvas announcement (discussion topic) ID'), which clarifies their purpose beyond type hints. However, it does not detail sources or valid ranges, so contribution is modest.

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 purpose: 'Get a single announcement with full body.' It specifies the verb 'Get' and resource 'announcement', and distinguishes this tool from its sibling 'get_announcements' by emphasizing 'single'. The return fields are listed, providing additional clarity.

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 does not explicitly state when to use this tool versus alternatives. While the sibling 'get_announcements' implies a plural listing, there is no direct guidance on selection criteria or exclusions. Usage is inferred from context but not articulated.

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