get_squad

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states that the tool gets a squad with members, which implies a read operation but does not explicitly confirm it is read-only, nor does it mention error behavior, permissions, or response format. The phrase 'with its members' hints at nesting but is vague.

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, direct sentence with no redundant words. It is front-loaded and effectively communicates the core function. This is appropriate conciseness, not under-specification (which is covered elsewhere).

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 has no output schema and no annotations, so the description bears the responsibility for explaining return values and edge cases. It only states that members are included, not the structure of the response or any error conditions. The optional workspace_id behavior is only partially covered by the schema, and the description does not compensate for the missing return format.

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 50%: workspace_id has a description, but id does not. The tool description does not explain the 'id' parameter or how it relates to the squad, nor does it clarify the optional workspace_id. It adds no meaning beyond the schema, leaving the required parameter undocumented in the description.

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 'Get one squad with its members' uses a specific verb ('get'), identifies the resource ('squad'), and clarifies that members are included. This clearly distinguishes it from sibling tools like list_squad_members (which only lists members) and list_squads (which lists squads without necessarily including members).

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 (fetching a single squad with its members) but does not explicitly state when to use this tool over alternatives like list_squad_members or list_squads. No exclusions or alternative recommendations are provided, leaving the context to be inferred from the tool name and description.

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