get_infographic

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

With no annotations, the description carries the burden of behavioral disclosure. It states the response includes a full description and download link, which is useful, but it does not mention any prerequisites (e.g., requiring a valid domain) or potential error states. For a simple read operation this is adequate but not rich.

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, concise, front-loaded sentence that directly states the purpose and key output components. No filler or redundant information is present.

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 get-by-id tool with a clear output description, the description is nearly complete. It could optionally hint at using list_infographics to discover valid IDs or mention behavior for invalid IDs, but given the tool's simplicity, it adequately covers the core context.

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?

Both parameters (id and domain) already have clear descriptions in the schema, providing 100% schema coverage. The tool description adds no additional parameter-level meaning beyond what the schema provides, so a baseline score 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 ('Retrieve') and the resource ('details of a single BPS infographic'), including what is returned (full description and download link). This distinguishes it from sibling tools like list_infographics, which enumerates multiple items.

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 phrase 'single BPS infographic' implies this is for a specific item lookup, given an id and domain. However, it does not explicitly mention when to use list_infographics to first find the infographic, or contrast with other retrieval tools like get_publication.

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