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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the temporal scope ('Recent') and the general result contents, but does not disclose details like ordering, default limits, or whether results are cached or live. It is adequate but not rich.

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 short sentences, front-loaded with the core subject and contents, followed by a necessary exclusion. Every word earns its place with no wasted filler.

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 list tool with optional parameters, the description gives a good sense of what is returned, but the undocumented 'limit' parameter and absence of an output schema leave a meaningful gap. An agent knows the general purpose but not how to constrain or paginate results.

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 coverage is only 50% because the 'limit' parameter has no description, and the tool description does not clarify it. 'profile_id' is documented in the schema, but the description adds no parameter-level meaning. The agent is left to infer what 'limit' controls.

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 identifies the resource as 'Recent MinMax budget-analysis runs' and enumerates the type of data returned: scope, top performers, and campaigns running hot. The explicit 'NOT the automation approval inbox (that is automation_activity)' distinguishes it from the most likely sibling confusion.

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 explicitly tells the agent when this tool is appropriate — when recent MinMax budget-analysis results are needed — and directly warns against using it for the automation approval inbox, naming automation_activity as the correct alternative. This is clear routing guidance.

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