tokportal_get_comment_task

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds behavioral context: it returns only owned comment tasks and includes coverage blocking details and stable block reason. This goes beyond annotations and clarifies important agent-facing behavior.

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?

Two sentences, front-loaded with the primary action. Every word adds value; there is no redundancy or filler. Highly efficient for an agent to parse.

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 simple tool (single parameter, no output schema, rich annotations), the description covers the core functionality and partial output. It could be more complete by explicitly stating that it returns a single task or errors if not found, but the current level is adequate for most use cases.

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 100% schema description coverage, the baseline is 3. The tool description does not add any additional meaning or constraints beyond the schema's 'Comment task ID.' No further explanation is provided for the id parameter.

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 'Get a comment task' with a specific verb and resource. It goes beyond by specifying it returns an owned comment task and includes coverage blocking information, which distinguishes it from sibling list tools like tokportal_list_comment_tasks.

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 usage is implied by the required id parameter: it fetches a specific task by ID. However, the description does not explicitly state when to use this over alternatives (e.g., tokportal_list_comment_tasks to browse), and it provides no guidance on prerequisites or when not to use it.

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