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

With no annotations, the description carries the full burden. It usefully discloses a real side effect — an external assignee receives a submission link and an email only when send_email=true — but says nothing about whether an existing owner is replaced, what permissions are required, or whether notifications go to internal members.

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?

A single sentence that front-loads the action and packs the parameter detail efficiently, with no filler. The density is justified by the undocumented owner parameter, though the nested parenthetical makes it slightly harder to scan.

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 mutation tool with no annotations, no output schema, and 0% schema coverage, the description covers the hardest part (owner formats) but leaves two of three parameters and key behaviors (overwrite semantics, permissions, member notification) unaddressed.

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 0% and the owner property has no type at all, so the description must compensate. It does an excellent job documenting the three owner formats ('me', 'u:...' member id, and the external {name,email,send_email} object), but diligence_id and item_id remain completely undocumented in both schema and description.

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 states a specific verb+resource: it sets the responsible party ('responsável') for an item, which is distinct from sibling tools like invite_member or remove_item. It is clear what the tool does, though it does not explicitly name a sibling it replaces or is distinguished from.

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?

Usage is implied by the name and by the enumeration of valid owner forms, but there is no explicit when-to-use/when-not-to-use guidance, no mention of alternatives such as invite_member for adding people to the workspace, and no stated prerequisites.

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