fetch_task_readme

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

No annotations are provided, so the description carries the full burden. It explains that the tool fetches complete README documentation, returns readmeText and taskName, and includes an error field for failures. This adequately discloses the read-only nature and error handling, though it could mention side effects (none) explicitly.

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 front-loaded with the primary purpose in the first sentence, followed by a brief elaboration and structured Args/Returns. Every sentence provides value without redundancy, making it efficient and easy 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 presence of an output schema, the description adequately explains the return fields (readmeText, taskName, error) and the purpose. It could mention potential length or format of the readme, but overall it is sufficient for the tool's simplicity.

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?

The input schema has 0% description coverage, but the description adds 'name (str): The exact name of the task to retrieve README for', specifying that the name must be exact and is associated with a task. This compensates fully for the schema's lack of detail.

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 retrieves README documentation for a specific task by name, distinguishing it from siblings like fetch_rule_readme_documentaion and get_template_guidance. The verb 'fetch' and resource 'task readme' are specific and unambiguous.

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 indicates this is useful for understanding how to properly use a task in workflows, implying the context. However, it does not explicitly state when not to use it or mention alternative tools for rules or templates, which given many siblings would improve clarity.

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