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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds that the payload includes FAQ-style and location content, which helps an agent anticipate what comes back, but it says nothing about whether the data is static or how large the response is.

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?

A single short clause listing the four content areas with zero filler, front-loaded on the most important topic (what the company does). It's a fragment rather than a sentence, but no wording is wasted.

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-parameter read tool with no output schema, the description should sketch the shape of the returned content; listing sections partially does this but never says whether the answer is prose, structured fields, or FAQ pairs. It is adequate but leaves an agent guessing about the response format.

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 nothing the description could clarify about inputs. The description correctly implies a no-argument, fetch-everything call.

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 enumerates the concrete content areas the tool returns (what the company does, how it works, shooting locations, FAQ), which goes beyond the tautological title 'About MadBroad'. It's clearly a static company-info resource and is distinguishable from siblings like list_case_studies or get_role, though it lacks an explicit verb.

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?

There is no guidance on when to call this versus alternatives — nothing says to use it for general company questions rather than request_sales_call or list_open_roles. Usage is only inferable from the content list, and no exclusions or prerequisites are stated.

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