createPersonAttachment

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

With no annotations, the description must disclose behaviors. It covers the key behavioral constraints (external-only files, env var requirements, error on missing URI), but does not discuss side effects, idempotency, or permissions beyond env vars.

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?

Two concise sentences. First sentence states purpose; second sentence provides critical restrictions and error conditions. No unnecessary words.

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?

Given no output schema and four parameters, the description covers action, restrictions, required env vars, and error condition. It omits details about storage behavior or validation of personId, but remains sufficient for most agents.

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 has 100% coverage with brief descriptions. The description adds critical meaning: uri must be externally hosted and omission returns 403. This clarifies usage beyond the schema, which simply says 'File URI'.

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 action ('Attach an externally-hosted file to a person') and differentiates from siblings (e.g., createDealAttachment) by specifying 'person' and 'externally-hosted'. It also highlights a restriction ('Registered Systems Only'), making the purpose unambiguous.

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 explicitly states when to use (attach external file to a person) and what not to do (hosting uploads, omitting URI returns 403). It also provides context on required environment variables, but does not explicitly mention alternatives for file uploads.

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