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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering key behaviors. Description adds that subscriber_code is required, but lacks other behavioral context like pagination or response format.

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?

Description is not concise; it includes a generic header and lists multiple unrelated actions. The relevant info for this tool is embedded within a larger block, reducing clarity.

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?

Incomplete for a tool with 8 parameters and no output schema. Missing explanation of response structure, pagination, filtering, and default behavior. Does not compensate for schema's lack of descriptions.

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?

Input schema has 8 parameters with 0% description coverage. Only subscriber_code is explained in the description, leaving other parameters (status, product_id, etc.) undocumented and their roles unclear.

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 explicitly states 'switch_plan_plans: planos disponíveis pra troca (requer subscriber_code)' which clearly identifies the tool as listing available plans for switching. However, the description is cluttered with other actions, reducing focus on this specific tool.

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?

Minimal guidance: mentions requirement of subscriber_code but does not specify when to use this tool over siblings like hotmart_subscriptions_write_switch_plan or other list tools. No explicit when-not-to-use or alternative recommendations.

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