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

The description adds significant context beyond annotations: idempotent behavior ('re-approving an existing owner, or a missing/expired id, is a clean no-op'), additive nature, no displacement, and response structure on missing/expired ('ok:false only on missing/expired'). Annotations already declare idempotentHint=true and destructiveHint=false, which the description confirms and enriches. No contradictions.

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?

The description is lengthy but each sentence adds essential information: main action, multi-owner nuance, idempotence, return shape, and scope. It front-loads the core purpose. While it could be slightly more concise, there is no wasted text given the complexity of the operation.

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?

Despite no output schema, the description explicitly states the return fields: '{ ok, id, slug, founder_clerk_user_id, current_owners }'. It also specifies the required scope ('admin:ownership_review'). For a multi-owner, additive, idempotent tool, this provides a thorough understanding of behavior and results.

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 100% and includes descriptions for each parameter. The description adds value by explaining that 'confirm' and 'force' are deprecated/no-op and why ('additive approve never needs it'). It also clarifies that 'id' is the pending ownership request id. This goes beyond what the schema provides.

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 'Bind the requesting founder onto the StartupProfile' and explains the resulting action: 'drop the request from the queue, write the active-ownership index + an audit entry'. It also describes the effect on permissions: 'Once bound, that founder's agent/session may edit the page + post news'. This distinguishes it from sibling tools like ic_admin_reject_ownership and ic_admin_list_pending_ownership.

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 explains when to use the tool by highlighting the multi-owner additive nature: 'approving ADDS the requester to the owner set (the first owner becomes the primary founder_clerk_user_id, each subsequent one is appended) — NO existing owner is ever displaced'. It also clarifies that confirm/force are no-ops. However, it does not explicitly state when NOT to use it (e.g., reject situations), though it implies the context.

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