Copilot Money MCP

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

The description adds valuable behavioral context beyond the readOnlyHint annotation. It explains the two distinct data sources, what each provides (estimated frequency, confidence score, next expected date for pattern analysis; user-confirmed subscriptions for Copilot tracking), and that both are included by default. This gives the agent important understanding about how the tool works internally and what to expect in results.

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 efficiently structured in three sentences that each add value: first states the purpose, second explains the two data sources and their outputs, third clarifies default behavior. There's no wasted text, and key information is front-loaded about what the tool identifies and how it works.

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 read-only tool with comprehensive schema documentation but no output schema, the description provides good context about what the tool returns (estimated frequency, confidence scores, next expected dates, user-confirmed subscriptions) and how it works internally. However, it doesn't explain the format or structure of the returned data, which would be helpful given the absence of an output schema.

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?

With 100% schema description coverage, the input schema already documents all 7 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline expectation but doesn't provide additional semantic context about how parameters interact or affect results.

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 tool's purpose: 'Identify recurring/subscription charges' with specific details about the two data sources used (pattern analysis and Copilot's native subscription tracking). It distinguishes this from sibling tools like get_transactions by focusing specifically on recurring patterns rather than raw transaction data.

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 usage context by mentioning 'comprehensive coverage' and that both sources are included by default, but it doesn't explicitly state when to use this tool versus alternatives like get_transactions or how it relates to other financial analysis tools. No explicit when-not-to-use guidance or named alternatives are provided.

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