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

Goes well beyond the given annotations by disclosing the actual effect of the write (a public share link is created, or an invite-only share is upgraded to public) and by enumerating the response values (none, created, upgraded). The public-visibility warning is consistent with the destructiveHint=true and openWorldHint=true annotations.

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?

Three tight sentences, front-loaded with the action and its limit, then the safety warning, then the return signal. Nothing is redundant and nothing essential is buried.

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?

Even though an output schema exists, the description helpfully names the decisive return field (share_effect) and its values. With only two parameters, a mutation annotation set, and umambiguous schema coverage, an agent has everything needed to call this correctly.

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 the schema already documents both the verification_id source (verify_photo, verify_content_credentials, list_verifications) and the title's 80-character limit; the description only restates the title cap and adds the portfolio-level limit of 50.

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 of the account's verifications to the portfolio') plus a capacity constraint (max 50), which lets an agent tell it apart from update_portfolio_item or share_verification 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?

Gives an explicit pre-call instruction ('Tell the user before calling it'), which is real usage guidance, but it never names an alternative or exclusion (for example, when to use share_verification instead), so the guidance is clear but partial.

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