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

Goes well beyond the annotations by disclosing what the call returns (an approval URL), that the connector's name and configuration are preserved with only new tokens issued, that each call mints a fresh link (consistent with idempotentHint=false), and that secret-based connectors are refused with a redirect to set_env_vars. It adds a real prerequisite (connecting a Valet account) that no annotation conveys.

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?

Dense and front-loaded: the qualifying conditions and the return value come first, and no sentence is filler. Some clauses are convoluted ("the address the person opens to approve it"), which slightly hurts scanability but not substance.

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?

With no output schema, the description takes responsibility for describing the response shape (an approval address) and does so. Annotations cover the safety profile and the description covers prerequisites, refusal behavior, and side effects, leaving nothing an agent needs missing for this two-parameter tool.

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%, so both org_name (including the fallback-to-default-org rule) and connector are already fully documented in the schema. The description adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 (renew/reauthorize) plus the exact resource (an organization connector's authorization that runs in a browser) and narrows it to two qualifying cases: OAuth or Composio-managed connectors whose grant was revoked or whose initial authorization never completed. This distinguishes it cleanly from siblings like reauthorize_channel, attach_connector, or call_connector.

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 gives the when (provider-revoked grant, or a first authorization that never finished), the when-not (credentials stored as secrets are refused), and the alternative path for that case (use set_env_vars with the named secrets). It also states the prerequisite that a Valet account must be connected.

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