task_role

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

With no annotations, the description must fully disclose behavior. It mentions reading and updating, and states it does not start agents or change lifecycle. However, it does not cover side effects of updates, idempotency, or auth requirements. Additionally, the phrase 'update it with both status and summary' potentially contradicts the schema where both are optional.

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 concise sentences, with the main action clear in the first sentence and an important exclusion in the second. No wasted 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?

No output schema, no annotations, and 4 parameters. The description omits the 'json' parameter purpose, what 'focused guidance' means, and the return value format. It lacks sufficient detail for an agent to use correctly in all scenarios.

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%, so description must compensate. It mentions role, status, summary but not the 'json' parameter. It says 'update it with both status and summary' which may mislead agents into thinking both are required when they are not. No explanation of enum values or their meaning.

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 tool reads or updates a Task Passport role lane, distinguishing it from tools that start agents or change lifecycle. The verb 'read' and 'update' specify the actions, and the resource is 'Task Passport role lane'.

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 implies usage for reading current state or updating status/summary, and explicitly rules out starting agents or lifecycle changes, which helps differentiate from sibling tools like task_start or task_update. However, it does not explicitly state when to use this over alternatives like task_status.

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