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

The description mentions 'Stored as a name snapshot', which hints at behavior, and lists required parameters. However, it does not disclose side effects, permissions needed, or idempotency. Annotations provide no additional hints (readOnlyHint false, destructiveHint false), so the description carries the burden but is incomplete.

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 short (two sentences) but the second sentence is fragmented ('Stored as a name snapshot. op set/add/remove.'). It lacks clear structure and the term 'host' is unclear. Could be more readable without sacrificing length.

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 the tool's complexity (5 parameters, 6 entities, 3 ops) and no output schema, the description is too minimal. It omits return values, error handling, and full behavioral context. An agent would struggle to use it correctly without additional information.

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?

With schema description coverage at 0%, the description adds minimal parameter context beyond listing names. It notes 'Stored as a name snapshot' for role_id but does not explain op, entity, item_id, or event_id formats or semantics. The cryptic 'host' at the end is confusing. This does not compensate for the poor schema documentation.

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 'assign' and the resource 'role to production item,' specifying the entity types (tasks, receipts, etc.) and distinguishing between single and multiple items. It also lists the operations (set/add/remove). This provides a specific purpose that differentiates from generic role management tools.

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 does not explicitly state when to use this tool versus alternatives like add_role. It mentions 'op set/add/remove' but provides no guidance on choosing among them or when not to use the tool. No prerequisites or exclusions are given.

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