get_authorized_app

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

Annotations already indicate readOnlyHint=true, so safety is clear. Description adds return structure (id, name, description, users), which is helpful context beyond annotations. No mention of rate limits or auth, but sufficient for a 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?

Well-structured with clear title, usage guidance, args, and returns sections. No unnecessary words, every sentence adds value.

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 simple read tool with output schema, description covers return fields and main parameter. Could mention possible errors or limitations, but not required. Slight gap on 'account' parameter purpose.

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 has 2 params (app_id required, account optional) with 0% schema description coverage. Description only explains app_id ('the authorized app ID to inspect. Obtain from list_authorized_apps') but does not explain the 'account' parameter, leaving its purpose ambiguous.

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 it retrieves the full record for a single OAuth-authorized application, specifying verb 'retrieve' and resource 'authorized app'. Distinguishes from sibling 'list_authorized_apps' by noting it's for a single app when ID is known.

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?

Explicitly says 'Use when you have an app ID and need its name, description, or the users that authorized it' and suggests using list_authorized_apps to browse and discover IDs, providing clear when-to-use and alternative.

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