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

With no annotations, the description carries the burden. It discloses the tool returns conceptual model, relationships, and workflow rules, and enumerates valid entities. It does not describe failure behavior or output format, but for a read-only guide tool this is acceptable transparency.

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 front-loaded with the main purpose and provides essential details in a compact form. The list of entities is necessary and keeps the description self-contained. It is slightly long but every element contributes to understanding the tool.

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?

The tool is simple (one required parameter) and the description covers what it returns, what entities are available, and what kind of guidance it provides. It does not explain the return structure, but with no output schema that is less critical. The description is sufficiently complete for an agent to invoke it correctly.

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%, so baseline is 3. The description adds value by listing all valid entity values, going beyond the schema's example-based description. This fully compensates for any ambiguity in the schema and helps the agent select a correct entity.

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 returns a conceptual model and workflow guidance for an AdCritter entity, specifying what it is and how it relates to other entities. This distinguishes it from sibling tools like get_api_reference and get_design_guide, and the list of available entities makes the scope explicit.

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 says it includes 'exhaustive workflow sequencing and prescriptive rules so generated apps call the API correctly,' which implies when to use it: when you need to understand the intended workflow for an entity. It does not explicitly mention alternative tools or exclusions, but the context is clear enough for a simple guide lookup.

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