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

The readOnly/idempotent/non-destructive annotations already cover the safety profile, so the description's job is to add context — and it does, by asserting the content is 'verificado contra la app' (an authoritative, non-speculative source) and by prohibiting fabricated screens or spurious support escalation. It does not describe what form the guide content takes (structured feature list vs. prose), which would help an agent know what it is reading.

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?

Two sentences, front-loaded with scope then the imperative directive, with zero filler. The long comma-separated topic list is dense but each item genuinely delimits coverage; it could be marginally tightened but nothing is truly wasteful.

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 no-parameter, read-only lookup tool with no output schema and full annotation coverage, the description supplies scope plus the anti-hallucination rule that an agent most needs. The one gap is that it never says how to combine this with sibling knowledge tools when a question spans app mechanics and golf rules.

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?

The tool takes zero parameters and the schema is trivially complete, so the baseline of 4 applies. The description correctly does not invent parameter discussion.

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 names a concrete resource (a verified guide to how the Badgie Golf app works) and enumerates the covered domains: friends/guest rounds, peñas, tournaments, live scorecard, stats, handicap, swing analysis, Garmin/Apple Watch/TrackMan, Pro. That is far more specific than the title, but it never distinguishes itself from adjacent knowledge tools such as search_instruction, get_rule, explain_game_format or ask_morris, so an agent must infer the boundary.

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?

It gives an explicit, imperative trigger ('Úsala SIEMPRE antes de explicar dónde está algo o si se puede hacer en la app') plus two negative rules: never invent screens and never route to support for something answered here. When-to-use and when-not-to-use are both stated, which is rare.

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