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

Annotations indicate read-only, non-destructive, idempotent behavior. Description mentions output as raw TOON text, which aligns. Does not detail errors or side effects, but annotations cover safety, so transparency is adequate.

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?

Concise two-sentence description with no fluff. Information is directly relevant and well-structured.

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?

Covers core usage and defaults but lacks details on return format (though no output schema) and does not elaborate on all parameters or potential errors. Sufficient for basic use but not fully comprehensive.

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 0% description coverage for 8 parameters. Description mentions only 'from', 'reference', and 'page' (in defaults), leaving 'query', 'fileType', 'toolNames', 'folderReference', and 'excludeToolNames' unexplained. Significant gap in parameter guidance.

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?

Clearly states the tool searches user creations and returns raw TOON text. Also distinguishes from creations_get for single id, making its purpose specific.

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 an alternative (creations_get for one id) and describes key requirements like 'reference required with from=folder/project-root' and defaults for page. Lacks explicit exclusions for other search tools but overall gives useful usage context.

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