get_authorized_app

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

Annotations already declare readOnlyHint=true, so the 'Read-only, safe to retry' is consistent but redundant. The description adds behavioral context beyond annotations by stating 'Authenticated via API key' and 'Max 10 concurrent requests', which are not in annotations.

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?

Every sentence earns its place. The description is structured with a clear purpose statement, usage guidance, behavioral notes, and parameter descriptions. It is compact and front-loaded with the core action.

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?

The description covers the tool's purpose, usage context, authentication, concurrency limits, parameter details, and return format. With only 2 simple parameters and output schema existing, this is fully complete.

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 0%, so description carries full burden. It explains app_id source ('Obtain from list_authorized_apps') and account usage ('Optional account name... configured via MAILCHIMP_API_KEY_<NAME>... Omit to use the default account. See list_accounts.'), providing critical context not in schema.

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 verb 'Retrieve' and the resource 'full record for a single OAuth-authorized application'. It lists specific fields (name, description, users) and distinguishes from the sibling tool list_authorized_apps, which is for browsing all apps.

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 says when to use this tool ('when you have an app ID and need its name, description, or the users that authorized it') and when to use an alternative ('Use list_authorized_apps to browse all apps and discover IDs instead'). Also mentions authentication and concurrency limits.

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