bag_health_mcp__get_series_details

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds behavioral context beyond annotations by noting that available dimensions vary by series, so one should always check. No contradictions.

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 well-structured with XML tags for use case, important notes, and example. It is front-loaded with the core purpose. Slightly long but each part 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?

For a tool with one parameter and an output schema, the description covers all relevant aspects: what it returns, when to use it, and an example. It also warns about varying dimensions. Completeness is high.

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 single parameter series_id has a description in the schema that explains the format and suggests using list_series to discover IDs. The description reinforces this and provides an example. Although the schema description coverage metric is 0% for top-level params, the nested description and the tool description together add meaning.

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 it gets metadata and available filter values for a specific data series. It distinguishes from sibling tool bag_health_mcp__get_disease_data by noting it should be called first to know valid filter options.

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?

Explicitly says 'Always call this before bag_health_mcp__get_disease_data to know valid filter options.' Also provides a use case, important notes, and an example, giving clear guidance on when and how to use.

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