tempo_get_plans

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that from/to dates are required, which is a useful constraint, but does not disclose pagination behavior, default view behavior, or potential performance implications of broad queries.

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?

A single, front-loaded sentence states the verb, resource, and a key requirement without any filler. It is efficient and immediately conveys the core purpose.

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 15 parameters and no output schema, the description is minimal. It covers the essential purpose and required fields but omits guidance on pagination (limit/offset), the meaning of the 'view' parameter (though schema covers it), and typical usage patterns. Given the schema's thoroughness, it's adequate but not comprehensive.

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?

Schema description coverage is 100%, so all parameters are documented in the schema. The description only adds 'matching the given parameters' and 'requires from and to dates', which restates schema info without adding new semantic value. Baseline 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 tool retrieves a list of Tempo plans (resource allocations) and requires from/to dates. It distinguishes from the singular 'tempo_get_plan' by using 'list' and 'matching parameters', but does not explicitly name alternatives or scope limitations.

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?

It implies usage for fetching multiple plans with filters, but provides no explicit when-to-use vs. alternatives, no exclusions, and no guidance on pagination or view selection. The required dates are stated, but the description lacks a clear 'use this when' directive.

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