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

The description is consistent with the 'readOnlyHint' annotation (true). It adds no additional behavioral details beyond what the annotation already provides, such as side effects or permissions. For a simple read operation, this is adequate but not enhanced.

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 very concise: a single sentence plus a reference to the API endpoint. It is front-loaded with the purpose. The API endpoint reference adds context but is not essential. More weight could be added without being verbose.

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 tool with one required parameter and a readOnlyHint annotation, the description is complete enough. There is no output schema, but the return value (user object) is predictable from the purpose. The description covers the essential need.

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 schema description for 'userId' is 'The user id (required).' The tool description says 'by their id', which repeats the schema. With 100% schema coverage, the description adds no new meaning beyond what the input schema already provides.

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 purpose: 'Get a single user by their id.' The verb 'get' and resource 'single user' are specific and unambiguous. It distinguishes from sibling tools like 'squadcast_list_users' which retrieves all users.

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 provides no guidance on when to use this tool versus alternatives (e.g., list_users). The usage is implied by the function but no explicit when/when-not or exclusions are given.

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