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

With no annotations, the description carries the full burden and does disclose meaningful behavior: a hard cap of 100 results, ordering by most recent update, and caller-scoped visibility. It omits whether the read requires any permission and what each task record contains, but the core operational traits are stated.

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 sentences, front-loaded with the return behavior and scope before the usage guidance. No filler; every clause conveys a distinct fact.

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 simple optional-param read tool with no output schema, the description covers result cap, ordering, scope, and usage adequately. It could note the shape of returned tasks, but nothing essential to correct invocation is missing.

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 100% and the single parameter is optional, so the schema already documents namespace_slug fully. The description adds the scoping intent, but it refers to it as 'namespaceSlug' while the schema property is 'namespace_slug', a naming mismatch that adds minor friction rather than clarity.

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 with precise scope: tasks 'assigned to or created by the caller across all boards they can access.' This is clearly distinguishable from siblings like list_tasks, search_tasks, and get_task, which are not caller-scoped.

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?

Gives concrete use cases ('what's on my plate?', surfacing overdue/stale work) that make the intended trigger obvious. It does not, however, name alternatives or state when to prefer list_tasks or search_tasks instead, so it falls short of explicit routing.

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