pylon_get_teams

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

With no annotations provided, the description carries full burden. It states what data is returned (team names, member counts, specializations) but lacks critical behavioral details: whether results are paginated, sorted, filtered; authentication requirements; rate limits; error conditions; or whether this is a read-only operation (implied but not explicit).

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 efficient sentences: first states purpose and examples, second specifies return data. No wasted words, though it could be slightly more structured (e.g., separating purpose from return format).

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 zero-parameter read tool with no output schema, the description provides adequate basics (what it gets and what it returns) but misses important context: no output schema means the description should ideally detail return structure more precisely, and behavioral aspects like pagination/authentication are omitted.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on what the tool returns.

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 verb 'Get' and resource 'all support teams from Pylon', with specific examples of team types (Technical, Billing, Sales). It distinguishes from siblings like 'pylon_get_team' (singular) by specifying 'all' teams, but doesn't explicitly contrast with other get tools like 'pylon_get_accounts' or 'pylon_get_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?

No guidance is provided on when to use this tool versus alternatives. While it implies retrieving all teams, it doesn't specify prerequisites, timing considerations, or contrast with similar tools like 'pylon_get_team' (singular) or 'pylon_get_users' (which might overlap with team members).

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