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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description earns credit by disclosing the returned payload (identity fields plus available actions like request an audit, contact, book a meeting), which matters because no output schema exists. It does not mention auth, caching, or whether the profile is static per deployment, but those gaps are minor for a zero-parameter read.

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, no waste: the first front-loads the full contents of the profile, the second delivers the ordering instruction. Every clause carries information the agent can act on.

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 zero-param, read-only tool with no output schema, the description covers what it returns and when to call it, which is nearly everything an agent needs. Slightly more detail on the shape of the 'actions available' field (whether they are URLs or tool names to call) would make it fully complete.

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, so the baseline is 4 and there is no parameter meaning to add. The description correctly implies the tool is context-free by never referencing any input argument.

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 the specific resource ('Official profile of this brand') and enumerates exactly what it contains: name, description, tagline, contact details, website, social profiles, main location, and available actions. This clearly separates it from content-oriented siblings like get_services or get_offer. It stops short of explicitly naming a sibling it is not, which keeps it from a 5.

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?

'Use it first to know who the brand is' gives an explicit sequencing directive that tells the agent to call this before other brand tools, which is real usage guidance. It does not state when not to use it or name an alternative, so it lands at 4 rather than 5.

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