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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe read nature is covered. The description adds valuable behavioral context: insights are 'dated, sourced claim with its supporting figures,' which gives the agent a better understanding of the returned data structure and provenance, despite no mention of auth or rate limits.

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 a single, well-structured sentence that is front-loaded with the main subject and provides essential information without unnecessary words. It is concise and directly conveys the tool's purpose and source.

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?

The tool is relatively simple with two optional parameters and no output schema. The description gives a good overview of the data content but misses parameter semantics and does not describe the return format or how limit/subject affect results. This is adequate but leaves room for improvement.

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 0%, and the description does not mention the parameters (limit, subject) at all. Since there are two optional parameters, the description fails to explain their meaning or usage, leaving the agent to infer from the schema alone. This is a significant gap.

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 identifies the tool's purpose: retrieving Muffed's published editorial reads on the current NFL state. It specifies the resource ('editorial reads', '/trends board') and the nature of the content ('dated, sourced claim with its supporting figures'), distinguishing it from sibling tools focused on metrics, backfield data, or league info.

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 implies usage in the context of wanting current editorial insights from Muffed, but it does not explicitly state when to prefer this tool over alternatives or provide exclusions. There is no reference to other tools (e.g., for metrics use get_player_metrics), so guidance is implicit rather than explicit.

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