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

Annotations already declare idempotentHint=false, but the description makes the consequence concrete ('calling it twice creates two tasks'), which is genuine added value for a mutation tool. It also discloses the underlying endpoint (POST /todos). It does not mention permission or auth requirements, and destructiveHint=false is simply consistent with the text rather than elaborated.

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?

Three short sentences with the write marker front-loaded, then the key non-idempotency warning, then the endpoint. Nothing is wasted and nothing important is buried.

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 output schema, it covers the write semantics, idempotency behaviour, and endpoint, and annotations carry the safety profile. What is missing is minor: no mention of what the call returns or how failures on invalid user_id/task_type_id manifest.

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 all six parameters are already documented, including the street_list_users and street_list_task_types lookup hints. The description restates the optional user assignment and task type but adds no format or constraint detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('create a task (to-do) in Street') and scopes it with the optional assignment and task type. The resource is clearly distinct from siblings like street_create_note or street_create_follow_up, though it never names those alternatives explicitly.

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?

No explicit when-to-use guidance or exclusion against sibling creation tools such as street_create_enquiry, street_create_follow_up, or street_create_note. Usage is only implied by the resource being created.

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