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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the call is read-only, not what an 'idea' record contains, not how results are ordered or bounded. The only behavioral hint is the implicit read semantics of the name 'list_ideas', which the description itself never confirms.

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 single short sentence is not verbose, but its brevity comes from under-specification rather than economy — it is a fragment that conveys almost no information. There is no front-loaded statement of what the tool does, because no such statement exists.

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?

Complexity is low (no parameters, no output schema), but the description still leaves the essential question unanswered: what an 'idea' is, what fields come back, and when to prefer this over the many sibling list tools. For a simple tool a single clarifying clause would have sufficed, and even that is absent.

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 input schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies for a zero-parameter tool.

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 is a noun fragment ("The recurring engineering principles") that names a subject area but never states an action, so it never says the tool lists anything. It hints at the resource being 'ideas' but gives no verb and no differentiation from siblings like list_capabilities or list_systems — an agent cannot tell what this returns versus those.

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 when-to-use guidance, no exclusions, and no mention of any of the ten sibling tools. Nothing in the text tells an agent which situation should select list_ideas over list_capabilities, list_systems, or search_portfolio.

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