list_service_orgs

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

Annotations already declare readOnlyHint and destructiveHint. The description adds useful behavioral details: default single page, auto-pagination behavior, format support, and nuanced explanation of the select parameter (filters rows, not fields) with syntax and error handling. No contradictions.

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 extremely concise: one sentence for purpose, then two actionable tips. Every sentence earns its place with no filler. Front-loaded with the core verb and resource.

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 list tool with 7 optional parameters and no output schema, the description covers the key behaviors (pagination, format, select semantics) adequately. However, it omits the structure of the return value (e.g., JSON array), which could be helpful for an agent.

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 coverage is 100%, providing baseline 3. The description adds significant value by clarifying the misleading 'select' parameter (filtering rows, not picking fields), giving syntax examples, warning about unsupported fields, and explaining that all=true overrides pageNumber/pageSize. This goes well beyond the schema.

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 'Retrieve a list of all service organizations' with a specific verb and resource. Among sibling tools like list_customers and list_devices, it uniquely identifies the target as service organizations.

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 explicit context for using parameters like all and format, indicating when to auto-paginate or get CSV output. However, it does not explicitly differentiate from get_service_org or state when not to use this tool.

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