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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description adds nothing beyond the route, not even that this returns the schedule lines for a single budget or what happens with an unknown id; the describe_operation pointer is the only added value.

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?

Two literally identical sentences, so half the content is pure waste. The remaining content is a route string with no front-loaded explanation of 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?

A nested-object schema with 0% field descriptions, no output schema and no annotations gap filled by prose. For a tool whose only parameter is an opaque id, the agent is left without any notion of the return shape or the meaning of the path id, making the definition inadequate to invoke confidently.

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 0% and the description says nothing about the required 'params.id' or the free-form 'query' object. The agent learns neither what the id refers to nor what query parameters are accepted, so the description does not compensate for the schema gap at all.

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 is the raw route string 'GET /api/cam/annual-budgets/:id/schedule' repeated twice, which restates the title verbatim. It does identify a resource (annual budget schedule) and a read verb through the URL path, but offers no plain-language statement of what the operation returns or how it differs from the sibling get_cam_annual_budgets_c03116baf9909d96631ab195.

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?

There is no when-to-use guidance and no comparison to alternatives such as the annual budgets list tool. The only actionable hint is the pointer to describe_operation, which tells the agent how to get the request schema but not when to select this tool.

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