authorization

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

No annotations provided, so description carries full burden. It mentions required parameters and gives appPath formatting examples, but does not disclose side effects, authorization state changes, or potential errors. Incomplete for a management 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?

Description is relatively concise with examples and formatting. Every sentence adds information, though the contradiction with schema costs a point.

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?

No output schema, no annotations, and schema empty. Description tries to fill gaps but misses return behavior, prerequisites, and error conditions. Incomplete for a tool requiring multiple inputs.

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?

Description details parameters (action, appPath, interactive) that the input schema does not include (empty schema). Schema coverage is 100% empty, so description adds meaning but contradicts the schema, creating confusion.

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?

Description clearly states it manages app authorization for OID sync, listing specific actions. Distinguishes from sibling tools (allocate_id, analyze_workspace, config) by focusing on authorization.

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?

Lists required inputs (action, appPath) but provides no when-to-use guidance or alternatives. Sibling tools suggest authorization is a distinct operation, but no explicit usage context.

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