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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the closing "Read only." is redundant. The description does add genuinely new behavior: a bounded result size ("up to 3 sections") and the structure of each section (docs link plus app location such as Ads → Sales), which tells the agent what a useful vs. empty response looks like.

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?

Front-loaded with the resource and its scope, then the call trigger, then the fallback — a sensible order with no filler. The only waste is the trailing "Read only.", which restates the readOnlyHint annotation.

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 single-parameter lookup tool with a full schema and an output schema, nothing material is missing: scope, trigger, expected result shape, and empty-result handling are all covered.

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% and the single parameter is fully documented with its own examples, so the schema does the heavy lifting. The description still adds meaning by scoping what counts as a valid query (Siren itself: locations, features, pricing, credits, policies), which the schema's generic "question in plain words" does not.

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?

States a specific verb and resource ("Look up Siren itself") and enumerates the content domains it covers: app locations (pages, tabs, buttons), feature behavior, plans, prices, credits, policies. This clearly separates it from every sibling, which are all operational ad/studio/media tools.

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?

Gives an explicit trigger ("Call it before telling the human where to click or what something costs") and an explicit failure path ("if it returns nothing, say you're not sure and point to https://mysiren.ai/docs"). No sibling alternatives are named, but the domain is disjoint enough that none are needed.

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