MCP Multi-Chart Context

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

Annotations (readOnlyHint=true, destructiveHint=false) already inform the agent of safety traits. The description adds no behavioral details beyond what annotations provide, so it neither contradicts nor enhances 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 extremely short (one sentence plus a group tag). While concise, it sacrifices informativeness for brevity. It could be restructured to include essential details without becoming bloated.

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?

With a complex parameter (array of objects with many fields), no output schema, and no description of return value, the description is incomplete. It fails to explain what 'context' is returned or how the tool behaves across multiple charts.

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 tool description itself offers no parameter guidance, but the input schema includes a description for the array items explaining required fields and defaults. However, the description does not clarify that 'inputs' accepts multiple birth data objects (minItems 2), which is a key semantic detail.

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 states 'Compact context for MCP agents working across multiple charts,' which indicates the general domain but does not specify the actual operation (e.g., compute, summarize, compare). It is too vague to distinguish from siblings like 'chart' or 'composite'.

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?

No guidance is provided on when to use this tool versus alternatives, nor are any prerequisites or exclusions mentioned. The description lacks any usage context.

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