pylon_get_accounts

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 describes the operation as a read ('Get') and outlines what data is returned ('account details like company name, subscription level, and contact information'), which is helpful. However, it lacks details on behavioral traits such as pagination, rate limits, authentication requirements, or error handling, which are important for a tool that fetches 'all' accounts.

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 two sentences that are front-loaded with the core purpose and follow with additional context. Every sentence adds value: the first defines the action and resource, and the second explains what accounts are and what details are returned. There is no wasted text.

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 complexity (a read operation with no parameters but fetching 'all' accounts), no annotations, and no output schema, the description is adequate but incomplete. It covers the purpose and return data types but misses important context like response format, pagination, or potential limitations (e.g., large result sets). For a tool with no structured output, more detail on the return structure would be beneficial.

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 parameters with 100% coverage, so no parameters need documentation. The description doesn't add parameter details, which is fine here, but it could have mentioned if there are implicit parameters (e.g., sorting or filtering options). Baseline is 4 for 0 parameters, as it doesn't need to compensate for gaps.

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 customer accounts from Pylon'), specifies the scope ('all'), and distinguishes it from the sibling tool 'pylon_get_account' (singular) by emphasizing it returns multiple accounts. It also explains what accounts represent ('companies or organizations that use your service').

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 context by stating it retrieves 'all customer accounts,' suggesting it's for bulk retrieval rather than looking up a specific account (which would use 'pylon_get_account'). However, it doesn't explicitly state when not to use it or mention alternatives like searching or filtering, which are available in sibling tools like 'pylon_search_contacts' or 'pylon_search_issues'.

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