createPersonAttachment

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does add useful information about access restrictions and environment variables, but it does not describe what the operation does beyond 'attach', whether it creates a new record, or any side effects. There is no contradiction with annotations since none exist.

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 two sentences, gets straight to the point, and every part earns its place. It states the core purpose first and then provides the critical access constraint.

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 simple create operation with a fully documented schema, the description covers the essential context: what it does and the access restriction. It doesn't explain return values, but given no output schema, the absence is forgivable. The constraint about env vars is valuable and complete enough for this 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 the schema already documents all four parameters. The description adds minimal parameter-specific context, aside from implying the 'uri' is an external file reference. This meets the baseline but doesn't enhance schema semantics.

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) and the resource (externally-hosted file to a person), and it naturally distinguishes from sibling tools like getPersonAttachment and updatePersonAttachment by focusing on the create operation. The phrase 'externally-hosted file' adds specificity beyond a generic attach.

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 includes a notable usage constraint: 'Restricted - Registered Systems Only' and lists required environment variables. This gives clear context about when this tool can be used, though it doesn't explicitly name alternative tools or state when not to use it.

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