Log time using an Asana task GID (workflow)

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

Annotations already indicate the tool is not read-only (readOnlyHint=false) and not idempotent. The description adds context about error codes (404, 409) and the wrapper nature, which goes beyond annotations but does not contradict them.

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 well-structured with a clear purpose first, then usage, args, returns, examples, and error handling. It is slightly verbose in repeating 'same as everhour_log_time' for multiple params but efficiently uses front-loading.

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 complexity (6 params, no output schema, nested objects), the description covers purpose, usage, error handling, examples, and references sibling for param details. It is complete enough for an AI agent to invoke correctly, though it could include a note on the exact return shape.

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 33%, but the description adds significant value: it explains the asana_task_gid parameter thoroughly, provides examples, and references everhour_log_time for common parameters. This compensates for the lack of schema descriptions on three parameters.

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 ('log time') and the resource ('Everhour task that mirrors a given Asana task GID'). It distinguishes from siblings by noting it's equivalent to everhour_log_time with a constructed ID, avoiding the need to construct the ID manually.

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 says 'Use this when the user gives you an Asana ticket URL/GID and asks to log hours.' It also provides error handling with alternatives: 404 suggests Asana task not synced, 409 suggests using everhour_update_time_record.

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