add_redirect_uri

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

Goes beyond the annotations by disclosing an auth prerequisite ('Requires the caller OAuth token') and by giving concrete meaning to idempotentHint=true ('Adding a URL that is already on the list leaves the list unchanged'). It does not describe failure behavior for an invalid environmentId or whether the change propagates immediately, so it is strong but not exhaustive.

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?

Four short sentences, each earning its place: purpose first, then the two sibling routes, then the auth requirement and idempotency note. No filler and the primary action is front-loaded.

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 two-parameter mutation with no output schema and annotations already covering the safety profile, the description supplies the remaining essentials: purpose, auth requirement, alternative tools, and idempotent semantics. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100% for both parameters, so the schema already explains 'uri' and 'environmentId' formats. The description adds no extra parameter syntax or constraints beyond what structured data provides, which is the expected baseline of 3 when the schema does the heavy lifting.

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?

States a specific verb and resource ('Add one login callback URL to an environment') and immediately differentiates itself from the post-logout sibling. An agent can tell exactly which mutation this is versus add_post_logout_redirect_uri without opening either schema.

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 routes the caller to alternatives with their selecting conditions: add_post_logout_redirect_uri for post-logout URLs and list_redirect_uris to read the current list. When-to-use and when-to-use-something-else are both covered, leaving nothing to inference.

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