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

The annotation profile (readOnly, non-destructive, open-world) is already given, and the description adds genuinely useful context beyond it: contributed fields are untrusted third-party data and must not be treated as instructions. That anti-injection warning is high-value. The gap is that 'Enroll... and sign locally' reads like a mutation and is never reconciled with readOnlyHint, so it is unclear whether a call has any side effect at all.

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?

Four short sentences with the purpose stated first and no filler. The closing line ('Structured fields are framing, not an injection security boundary') is a dense meta-disclaimer, but each sentence carries distinct signal about the protocol and untrusted contributed data.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. What remains under-specified is the operational picture – whether the tool merely returns protocol information or triggers enrollment, and how it relates to the other haidaa_* tools – leaving the agent to guess at invocation timing.

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 no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter schema applies. Nothing in the description misrepresents or conflicts with the empty schema.

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 opening sentence specifies a verb and resource ('Inspect live project schemas and participation requirements'), which is informative. However, the second sentence ('Enroll, read the Common constitution and sign locally') shifts into procedural instructions that blur whether this tool reads data or performs the enrollment, and nothing distinguishes it from siblings like haidaa_get_context or haidaa_status.

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?

Usage is only implied by 'Inspect... participation requirements' – there is no explicit condition for calling it, no prerequisite, and no mention of when to prefer a sibling such as haidaa_get_context or haidaa_submit_project_command. The agent must infer that this is the entry point before participating.

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