Get Business Context

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety and idempotency. The description adds context on return value breadth (aggregated data types), which is useful but does not go beyond what annotations imply for behavior.

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 English description is concise with two front-loaded sentences that convey purpose and usage. The repeated Spanish translation adds redundancy but does not significantly detract; overall it is efficient for an AI agent.

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?

Given no parameters and no output schema, the description adequately covers the tool's purpose, return data categories, and primary use case. It is complete for an AI agent to understand when and why to invoke this tool.

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?

There are no parameters; schema coverage is 100%. Baseline for 0 parameters is 4. The description correctly omits parameter details and adds value by listing the data categories returned.

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 complete business context including profile, defaults, plan limits, recent activity, top clients, and current month summary. It uses specific verbs and resources, and distinguishes itself from siblings by positioning itself as the initial session call.

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 explicitly instructs to call this tool 'FIRST in any session' to understand the user's business, providing clear when-to-use guidance. It lacks explicit when-not-to-use or alternative tools, but the stated purpose is sufficiently directional.

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