List Shared Preconditions

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

No annotations are provided, so the description carries full burden. It does not disclose pagination, result limits, permissions, or default behavior. The only behavioral hint is the sorting and include option, but critical aspects are missing.

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 with two sentences. The first states purpose and features, the second provides a practical usage tip. No unnecessary words.

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 existence of an output schema, return values are not needed. However, the description lacks information on pagination, defaults (e.g., sort order), and differentiation from siblings, making it somewhat incomplete for a list tool.

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 has 100% description coverage. The description reinforces the sorting and include feature but adds little new meaning beyond the schema. The usage tip about 'id' is helpful but not parameter-specific.

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 that the tool lists shared preconditions for a project, and mentions sorting and optional fields. However, it does not explicitly distinguish from sibling 'get_shared_precondition' for single items, relying on the verb 'list' vs 'get'.

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?

Provides a usage tip for using the returned id in other tools, but lacks explicit guidance on when to use this tool versus alternatives like get_shared_precondition or list_shared_steps. No mention of prerequisites beyond projectCode.

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