apps_list

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

Annotations already indicate safe read operations. The description adds important behavioral details: cursor-based pagination, default page size, error on invalid includePrivate, and dual output modes (summary vs raw). This adds value beyond annotations.

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 concise, packing essential information in a single paragraph. It could benefit from bullet points for readability, but it is front-loaded with the core purpose and well-organized.

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?

Despite lacking an output schema, the description lists returned fields and explains pagination and output modes. It covers key aspects for a listing tool, though error handling beyond includePrivate is 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?

Input schema covers all 4 parameters with descriptions. The description reinforces key semantics: cursor usage, default limit of 10, effect of includeFullPayload, and error on invalid includePrivate. It adds practical context 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 the tool lists apps in a developer space, mentioning the fields returned and that it's a live API call. It doesn't explicitly distinguish from siblings like developer_space_listings or apps_known, but the name and context make its purpose clear.

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 explains pagination, parameters like includePrivate and includeFullPayload, and defaults. However, it lacks guidance on when to use this tool versus alternative listing tools, nor does it specify prerequisites or exclusions.

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