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

No annotations are provided, so the description carries the full burden. It implies a comparison against a national median but does not disclose what the tool returns (a number, a string, a detailed report), whether it mutates anything (unlikely but unstated), or how the capital-growth impact is derived. The description is too terse to convey behavioral traits beyond the basic 'reports a share'.

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 a single sentence, which is efficient. It front-loads the key concept ('single-parent-family share for the suburb') and includes the comparison context and the capital-growth impact. However, the phrase 'against the pinned national median' is slightly cryptic—'pinned' is jargon that might confuse an agent. No significant waste, but clarity could be improved.

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 has an output schema, which helps, but the description is minimal for a tool that seemingly computes a derived metric (share against median, impact). The complexity is moderate: it needs to clarify what 'single-parent-family share' means, how the capital-growth impact is expressed, and the format of the output. Without this, an agent cannot fully anticipate the result. The description is adequate for a simple lookup, but the mention of capital-growth impact implies additional complexity that is unexplained.

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 single parameter, suburb_name, is typed as string with no schema description (0% coverage). The description names the resource as a 'suburb', so it's reasonable that suburb_name is required. However, the description does not clarify the expected format (e.g., full suburb name, state abbreviation) or whether it must be a validated suburb from suburbs_list. With only one parameter and the context, this is adequate but could be improved.

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 states a clear verb ('share') and resource ('single-parent-family share for the suburb'), and mentions the pinned national median and capital-growth impact, which hints at its analytical purpose. However, it does not explicitly say what operation it performs (e.g., 'returns', 'calculates'), and the phrase 'associated capital-growth impact' is ambiguous—does the tool compute the impact or just report the share? It also doesn't distinguish from the many sibling suburbs_demographics_* tools that also cover single-parent data.

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?

No guidance is provided on when to use this tool versus the many related siblings such as suburbs_demographics_all, suburbs_demographics_cohorts, or suburbs_risks_capital_growth_impact. The description lacks context on whether this is a niche tool for comparing single-parent share against the national median or if it would be superseded by a broader demographic tool. The agent must infer use from the name alone.

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