Get Poem

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

Annotations declare readOnlyHint=true, and the description is consistent. However, no additional behavioral details are given (e.g., behavior if ID not found, or any constraints). Since annotations already cover the read-only nature, the description adds minimal extra transparency.

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, short sentence that front-loads the purpose without extraneous words. It is concise and to the point, though it could include a bit more context about 'pplog'.

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, read-only tool with one well-documented parameter, the description adequately conveys the core functionality. It does not elaborate on return values or error handling, but given the absence of an output schema and the tool's simplicity, the description is 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 has 100% coverage with description 'Poem ID' for the only parameter. The description does not add further meaning or format details; thus, it meets the baseline expectation without adding extra value.

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 'Retrieves', the resource 'a poem', and the method 'by ID'. It effectively distinguishes from siblings: 'create-poem' is a write operation, 'search-poems' is a query, while this tool is a direct fetch by ID.

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 implies use when you have a specific ID, but does not provide explicit guidance on when to use this tool versus the sibling 'search-poems', nor does it mention any prerequisites or context for appropriate use.

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