Start setup

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

Annotations indicate mutation (readOnlyHint=false). Description adds context about returning authorization link and saving credentials, but does not disclose side effects or what modifications occur. Lacks depth for a non-read-only tool.

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 sentences, no wasted words. Front-loaded with main action. Efficiently conveys the core purpose and optional parameters.

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?

Tool is part of a multi-step setup flow. Description covers the high-level action but lacks details on what happens without credentials, output format, or next steps. No output schema, so description could add more.

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 100%, baseline 3. Description adds value by explaining that passing clientId/clientSecret saves them, beyond the schema descriptions. This clarifies intent and optional behavior.

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?

Clearly states 'Begin or resume setup' and mentions creating a Yahoo app and returning authorization link. Distinguishes from sibling tools like fantasy_authorize by focusing on initial setup, but does not explicitly contrast.

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?

Implied usage for starting or resuming setup, but no explicit guidance on when to use vs. alternatives like fantasy_authorize. Mentions optional parameters but not prerequisites or context.

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