sigsci_list_corp_rules

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

No annotations are provided, so the description must fully disclose behavior. It states the tool lists rules (read operation) but does not reveal that pagination parameters (page, limit) are available, nor does it mention the type filter. Lacks details on whether the operation is read-only, destructive, or requires specific permissions.

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 that efficiently conveys the core function. No extraneous words or redundant information. Perfectly concise for the task.

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?

No output schema exists, so the description should hint at return format (e.g., array of rules). It does not. With 4 parameters, a simple list operation, the description is functional but lacks completeness about pagination or filtering behavior. Adequate but not thorough.

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?

Schema coverage is 100%, and parameter descriptions are present in the schema. The description does not add additional meaning beyond 'list all rules in a corporation'. It does not explain how parameters like type, page, or limit affect the result. Baseline 3 is appropriate since schema handles parameter documentation.

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 'List all rules in a corporation' clearly states the verb (list), resource (rules), and scope (corporation). It distinguishes this tool from siblings like sigsci_list_site_rules (site-level) and sigsci_get_corp_rule (single rule), making purpose unambiguous.

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?

The description implies usage for listing corporation-level rules but does not explicitly state when to use this tool versus alternatives like sigsci_list_site_rules or sigsci_get_corp_rule. No when-not-to-use guidance or prerequisite conditions are provided.

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